Repository navigation
ci: validate equivalent staged native test budgets - #1070
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
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.
The validator rejects the reviewed staged native-test budget when the equivalent
-timeout=15mflag follows the package list. This adds a bounded, base-derived equivalence check and passes its verified policy to the full scanner only after every independent authority check passes.The authority-boundary tests now read the existing CI YAML through a confined, hash-checked fixture reader. This removes the duplicated CI audit patterns from Go source, which caused the first head's AWS audit failure. Only the exact reviewed baseline and suffix-budget YAML hashes are accepted; both reproduce the original fixture bytes. The AWS audit itself is unchanged and still rejects a genuine banned import.
The total PR remains limited to the original five files: validator, validator tests, wrapper, authority fingerprints, and existing wrapper executable fingerprints. This correction changes one test file plus its mechanically derived wrapper/H/E hashes. The occupied 38-file staged bundle, policy contexts, command/action/presence/secret maps, module floor, guard, harness, native CI command, and permissions remain exact.
Validation:
64844620aca08bd15a84952078d548c0c4bd8bced3e46c3e0958925e7ad42c08.The owner approved the r154 reader correction and matching fingerprints on October 15 at 17:48 UTC within this PR's existing one-time admission. Admission is bound to source commit
46849af53dd688e968cbd23e001824a01e5d2714, tree6f90db0e91998849d9be25cfbc0976f92d05f32b, and the same original five owners. It expires after PR #1070 and its first main policy event; exact restoration of those same five beforeimages remains the bounded rollback scope. The expected old-base policy rejection stays visible. No false success, AWS/native/required/security waiver, settings change, manual rerun, downstream work, or standing admission is included.Related: #1066, #1069.