Repository navigation
test(orchestration): guard wide catalog listing with a same-run ratio - #1352
Merged
Merged
Conversation
The 3,000-node listing guard used a fixed 450 ms median, which hosted runners exceed by runner speed alone (480-530 ms on code that lists in about 210 ms locally). It now times the listing at 1,000 and 3,000 nodes in the same run and requires the larger listing to stay within six times the smaller: linear listing measures about three times, quadratic about nine.
kvlonge
enabled auto-merge (squash)
November 7, 2026 18:23
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.
Why
The catalog listing guard for a 3,000-node target required a fixed median under 450 ms. Hosted runners exceed that through runner speed alone: 480–530 ms on three unrelated pull requests, for code that lists in about 210 ms locally. Absolute budgets on hosted runners are not a reliable regression signal, so it failed CI without any code change.
Changes
Verification
cargo test -p sqlbuild-orchestration --lib test_catalog_readson SQLite and PostgreSQL, three runs each: ratios 2.6–3.3 at load average 2.4 on 8 cores.make check-cipasses locally.DuckShop: not applicable; this changes a control-store test's timing check, with no project shape, data value or lifecycle sequence.