-
test: give the 10k-iteration sort-key property test its own timeout
All checks were successfulCI / Lint, typecheck, test (pull_request) Successful in 6m45sCI / Build container images (pull_request) Successful in 2m51sCI / Auth e2e pack (pull_request) Successful in 8m54sCI / Import/export fidelity gate (pull_request) Successful in 58sCD / Build and push images (push) Successful in 15sCD / Deploy to Test (push) Successful in 16sCD / Smoke tests against Test (push) Successful in 1m17sCD / Promote to Int (push) Successful in 13sCI / Lint, typecheck, test (push) Successful in 6m52sCI / Build container images (push) Has been skippedCI / Auth e2e pack (push) Successful in 8m43sRelease / Build release images and notes (push) Successful in 2m48sCI / Import/export fidelity gate (push) Successful in 56sRelease / Release-candidate operations QA (push) Successful in 56sProd deploy / Deploy the released images to Prod (push) Successful in 17sreleased this
2026-08-02 14:01:14 +02:00 | 15 commits to main since this releaseUnder parallel CI load the test repeatedly exceeded the default 5000 ms
per-test timeout (run 685 on main, run 699 on an unrelated PR); the
identical test passed on rerun. Locally it finishes in about 1.3 s, so
30 s is generous headroom, not a mask for a regression.Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_017aviRTgWCcAHUh1SBoxf6PDownloads