Repository navigation
Conversation
…ndpoints already uses The wait spans the opaque compiling phase, so it cannot follow progress. Since #607 reshuffled the shards it has failed at 360 s on 3 of 4 master runs (3.12 and 3.14), with passing runs at 90-340 s. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AWjnwpYHm56hSpKBzbPhrG
This branch has not been deployed
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
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.
`test_run_lifecycle_status_snapshot_and_graceful_stop` waits for a short kelt4 fit to reach 100 draws. It allowed 360 s and has failed at that limit on 3 of the last 4 master CI runs (3.12 and 3.14), with the run still in its `compiling` phase. Passing runs take 90-340 s, so the limit was marginal. The failures began when #607 refreshed `tests/durations.json`, which changes how tests are grouped onto CI shards.
This wait covers the whole `compiling` phase, which writes no status updates, so it can't be made progress-based. The change gives it 600 s, the budget `test_run_endpoints.py` already uses for the same wait. The timeout mark goes from 1320 s to 1560 s, so the worst-case sum (1510 s) still fits. Warm runs are unchanged at 57-81 s.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AWjnwpYHm56hSpKBzbPhrG