Repository navigation
test: interleaved ratio guard for retained metadata scans; mock runs keep their target - #1485
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.
Why
A warehouse-metadata test bounded a retained-history scan with a fixed five-second wall clock around ten write requests. Each request commits, and on a busy Windows runner the disk syncs alone sometimes pass five seconds, so the test failed without a code change. Separately, the mock UI printed ad-hoc and job runs launched in the demo with an empty
--target.Changes
--target prod.Verification
sqb build --select stg_orders --target prod.make check-ci.