fix: isolate perf workloads for verify budget#75
Merged
davidahmann merged 1 commit intomainfrom Feb 28, 2026
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.
Problem
v1release preflight was failing inscripts/test_perf_budgets.shon theverify_chaincommand budget.The perf harness measured command budgets against
state-100.jsonafter also running a 500-repo scan in the same temp directory. Because proof chains are keyed by state directory, the 100-repo verify checks were run against a chain that already included both workloads, inflating chain size and causing false failures.Changes
scripts/test_perf_budgets.shto isolate 100-repo and 500-repo scans into separate workspace roots.score,verify --chain,regress run) tied to the 100-repo workload chain only.Validation
scripts/test_perf_budgets.shscripts/run_v1_acceptance.sh --mode=releasemake prepush-full