ops: record artifact hashes, RAM limit, and resume regression#15
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Artifact identity completed
Records SHA-256 for:
step_60000.pt, sidecar and run manifestbest.ptand sidecarThe selected launch base remains
step_60000.pt;best.ptis not treated as equivalent.Dedup capacity decision
The larger source pools are recorded as conservative overlap references without claiming that each was the exact tokenization source.
Resume evidence correction
Replaces the earlier unreproducible “bit-identical” observation with the clean-checkout result:
Launch remains blocked until #14 is merged and the clean-checkout resume smoke passes with the fix.