Repository navigation
Track parity build provenance and generator inputs - #104
Merged
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
1 participant
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.
Summary
Parity builds discover the executable through Cargo and record compiler, target, feature, flags, output path, and binary hash. Oracle cache identity includes the selected executable bytes, and each parity run uses isolated outputs with immutable cache publication and stage-specific failures. Definition generation preserves output mtimes when formatted output is unchanged and writes an ignored per-unit receipt containing input/output hashes and coverage deltas.
Validation
cargo fmt --all --checkcargo clippy --workspace --all-targets -- -D warningscargo test -p xtask(68 passed)cargo check -p xedit-defsAccess is deniedin this restricted environment