Pick the run this test made, not the first one running
Docs / docs (push) Successful in 22s
Playwright Tests / test-playwright (1, 2) (push) Failing after 1m56s
Playwright Tests / test-playwright (2, 2) (push) Failing after 1m48s
pre-commit / pre-commit (push) Failing after 3m2s
Test Backend / test-backend (push) Successful in 2m26s
Compose Smoke Test / test-compose (push) Successful in 30s
Playwright Tests / merge-reports (push) Failing after 2m0s

The suite runs in a random order and a run left marked running by an
earlier module lands in the same list, so asserting on data[0] failed on
whichever seed put that module first.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Gf7WaExcJ9bs3kfJXB3nK
This commit is contained in:
2026-08-25 21:52:48 +02:00
co-authored by Claude Opus 5
parent 3af5342a2b
commit b194071ca5
@@ -278,7 +278,10 @@ def test_a_running_cascade_reports_how_long_it_has_been_going(
f"{PREFIX}/runs", headers=superuser_token_headers, params={"status": "running"}
).json()
assert runs["data"][0]["duration_ms"] >= 30_000
# By id rather than by position: another module can leave a run of its own
# still marked running, and the list is not this test's alone.
in_flight = next(r for r in runs["data"] if r["id"] == "in-flight")
assert in_flight["duration_ms"] >= 30_000
def test_events_narrow_to_one_minute(