Repository navigation
test: recall tests no longer race the 300 ms lookup bound - #220
Merged
Merged
Conversation
… machine The shared recall test host used timers that never fire, but the recall bound is measured from the clock's timestamps, which were the system's. Under CI load (floating-dependencies, PR #219) a lookup took over 300 ms and timed out. Tests on that clock now get a one-hour bound unless they set their own; the timeout test keeps its manual clock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GPXz56QPQAzDSyJTxbQTTy
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.
A recall test failed on floating-dependencies in PR #219: under CI load the lookup took over its 300 ms bound and timed out. The shared test host used timers that never fire, but the bound is measured from the clock's timestamps, which were the system's. Tests on that clock now get a one-hour bound unless they set their own; the timeout test keeps its manual clock. Test-only.
🤖 Generated with Claude Code
https://claude.ai/code/session_01GPXz56QPQAzDSyJTxbQTTy