test_upstream_returns_ok
test_N02_network_timeout.py · failed in 5% of captured runs
The failing run did not reach its assertion — it raised before getting there. That is not evidence about a schedule.
Where the two runs diverge
The same test, twice, on a shared time axis. The outlined pair is the ordering that differs.
read_response, assert never started in the failing run. The run flushed its spans normally, so that absence is evidence: the operation had not happened by the time the assertion read the state.
Evidence
Suspicion comes from comparing runs. The decision comes from forcing the ordering and seeing what happens.
No ordering differed between the passing and failing runs.
Policy gate
Every check the proposed patch had to pass before it was allowed to run.
No patch was proposed, so there was nothing for the policy gate to review.
Verification
What was established, and at which strength. A weaker check is never presented as proof.
Verification did not run: no patch reached it.