Repository navigation
tests: make SET start/end tests independent of the real date - #8
Merged
Merged
Conversation
…real date Six tests used the fixed 2026-10-03 SET window but read the real clock; after the SET ended they hit the (correct) post-SET lock and failed on main. Test-only change; verified the full suite passes with the clock shifted before, during, and a year after the SET.
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.
Fixes the red
mainbuild after v2.7.0. Six tests intests/test_set_messages.pyused the fixed 2026-10-03 SET window but read the real clock. After the SET ended, the (correct) post-SET lock refused their edits.Test-only change: the
applyfixture now pins the clock mid-SET. The full suite passes with the clock shifted to before, during, and a year after the SET.