Repository navigation
The required check's checks job may run 25 minutes, not 15 - #307
Conversation
…runs whose tests were still running On 2026-10-21 `make verify` on the runner, its simulators on 300 seeds, took 11 to 14.5 minutes, and six runs in three pull requests were cancelled at the 15-minute timeout with the tests still running. The Maintainer raised it to 25. The workflow, its example and the standard change together, with the measured times in the head comment, and the tests that broke the old value to show drift now break the new one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…at finished, and which timeout to raise before Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 25 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Main now holds the 25-minute checks timeout (#307). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>



The Maintainer raised the
checksjob's timeout from 15 to 25 minutes.Why
On 2026-10-21,
make verifyon the runner (its simulators on 300 seeds) took 11 to 14.5 minutes in the runs that finished. Six runs were cancelled at 15:00 with the tests still running:The mutation shards run the same suite on 40 seeds and pass, so the cancelled runs are slow, not broken.
What changes
.github/workflows/verify.yml:checksgetstimeout-minutes: 25. The head comment gains one line with the measured times.examples/workflows/verify.ymland the first yaml block ofdocs/standards/workflows.mdchange the same way. They hold the workflow word for word, andtools/check_workflows.pyandtools/check_context.pycompare them.tests/test_tools.py: the tests that removed or changedtimeout-minutes: 15to make a drift or a fault now use 25. Each still fails loudly if its replacement stops matching.Nothing else changes: no permission, trigger, secret, pin or step.
Gates
PATH=/usr/bin:/bin SIM_SEEDS=40 make verify: 973 tests, OK.🤖 Generated with Claude Code