Repository navigation
test: keep orchestration history fixtures inside a controlled time window - #14407
Merged
Merged
Conversation
diegosouzapw
marked this pull request as ready for review
September 24, 2026 00:42
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
1 participant
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.
Quality-gate recovery, QG-08. Exact release base 1853a61 reproduces 10 failures because fixtures dated 2026-09-01 expire against Date.now(). Freeze Date only, keep asynchronous scheduling real, and explicitly advance the clock for action completion. Assertions and production filters are unchanged. Validation: two consecutive full-file runs pass 14/14; the first patched run had 13 passes and one 5-second timeout, retained as evidence rather than hidden or relaxed. Hooks pass. Full integrated CI remains pending; no claim of release acceptance.