Repository navigation
test(queue): freeze the clock for usage display assertions - #127
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 usage-display test could cross a wall-clock second between creating a one-hour lease and rendering it, making the remaining time correctly render as minutes while the test required hours. Freeze the test clock at an integer second so the existing idle, owner, queue and release assertions remain deterministic. Production code is unchanged.
Validation: all 52 queue-bot tests pass; git diff --check passes. This addresses the Python 3.11 failure in PR #125 CI run 41780854082.