Repository navigation
Make the Antigravity eviction fixture independent of disk timing - #1015
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 main Windows ARM run failed while the cache-eviction fixture was creating 72 filler entries: it required every unrelated disk probe to return Primary within the production 200 ms listener deadline. A deadline can legitimately return Unverified, so that assertion prevented the test from reaching its eviction case (job 133803805324).
Fixture setup now uses the production cache-insertion function for known non-system step-zero records. The real probe worker is deliberately paused during setup, making this independence deterministic. The test still parses real cold-start and post-eviction child hooks, accepts the real parent, and asserts both the cache bound and parent eviction. The shared pause guard also retains the existing timeout/full-queue test behavior. Production limits and classification code are unchanged.
Validation: Rust formatting, architecture against
1516ae67, platform cfg (459/459), staged whitespace and name checks passed. Native Windows ARM run 44024087089 passed all seven subagent cases in each of three repetitions, with zero retries. Restoring the old filler-probe setup under the controlled pause reproduces its exact assertion failure. The PR policy selected Linux only; manual full-native run 44025219978 validates the same source on all five platforms before merge.