ci: Add more startup time for Matrix shards - #5795
Merged
Merged
Conversation
The 300s ceiling on the realm-server-ready wait is close enough to a healthy cold boot that the slowest matrix shard fails on it: the harness kills a server that reported progress milliseconds earlier, having nearly finished indexing the base realm. The comment above the constant assumed that boot takes ~2 minutes; the slowest shard's setup measures closer to five. Double the cap. It was never a performance assertion — the progress-aware watchdog beside it fails a boot that goes silent within 90s, so a genuine hang still surfaces just as fast, and only a server that keeps emitting output without ever finishing waits longer than before. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
backspace
marked this pull request as ready for review
August 17, 2026 19:06
lukemelia
approved these changes
Aug 17, 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
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.
I’m seeing Matrix shard failures in #5776 based on the 5min timeout described here, though the comment says 2min. Shards 1 and 3 are regularly approaching or exceeding 5min startup, which CS-12533 tracks for analysis and reduction. But for now, this raises the timeout to 10min.
Claude explanation
The 300s ceiling on the realm-server-ready wait is close enough to a healthy cold boot that the slowest matrix shard fails on it: the harness kills a server that reported progress milliseconds earlier, having nearly finished indexing the base realm. The comment above the constant assumed that boot takes ~2 minutes; the slowest shard's setup measures closer to five.Double the cap. It was never a performance assertion — the progress-aware watchdog beside it fails a boot that goes silent within 90s, so a genuine hang still surfaces just as fast, and only a server that keeps emitting output without ever finishing waits longer than before.