Raise default CI batch timeout from 3m to 15m#750
Merged
Conversation
The 3-minute default routinely expired before slow agents (codex, gemini) could finish, leaving PR comments with partial review counters. 15m gives realistic reviews room to complete while still bounding worst-case latency.
roborev: Combined Review (
|
mariusvniekerk
approved these changes
May 27, 2026
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
2 participants
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.
Summary
[ci].batch_timeoutfrom 3 minutes to 15 minutes inCIConfig.ResolvedBatchTimeout.1+0/3) and discarded output from still-running child processes.BatchTimeoutfield and the unit tests that assert the default.