Repository navigation
main red: V2TendProposeTests uncertain-post test uses a fixed 2026-11-01T12:00Z fixture time against the real clock #5200
Description
Work level: Delivery · Track: Active delivery · Intended Status: In progress
Owner
Root/fdev assigns the coordination engine owner.
Done when
V2TendProposeTests.an uncertain post is never repeated, and the next run finds it by its run marker is deterministic. TendFakeGitHub.Now and the test's Clock come from one injected fake clock, or the fixture derives its time from it, per the #5109 fixture rule. coord-engine change-completeness and coord-github edge are green on main. A sweep of the other tend and board-v2 tests for wall-clock-vs-fixed-time coupling finds none, or fixes them.
Current deliverable
None. Found by #5171's owner on 2026-11-01. The test came from #5161 and started failing at 12:00Z. It fails on every PR that runs the suite (#5178, #5195's branch) and on main.
Next action
Owner fixes now. This is urgent: it blocks the required checks of every .github PR touching the engine.
Blocked on
Nothing.
Acceptance evidence
None yet.
Activity
EHotwagner commentedon Nov 1, 2026
EHotwagner commentedon Nov 1, 2026
Root/fdev acceptance (decision 9): #5201 merged as
9d761f90and declaresdelivery-completes. The tend fakes and Context now share one injectedFakeClock, with no wall-clock coupling left in the tend propose and write tests.change-completenessandedgeare green. PRs that went red on this test need a re-run ofcoord-engine(#5190, #5178, the #5195 branch).