Repository navigation
ci(j5): give server test shards 25 minutes - #737
Conversation
The Chromium install step alone can take over eleven minutes on a cold runner, so server shards hit the 15-minute limit and were cancelled with no failing test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update server test timeout .github/workflows/j5-ci.yml |
The test_server job timeout changes from 15 to 25 minutes. A comment notes that Chromium installation can take over eleven minutes. |
Priority:
Estimated code review effort: 2 (Simple) | ~5 minutes
Change: Bug fix
Possibly related PRs
- Jacksondr5/j5code#662: This PR also changes the
test_servertimeout in.github/workflows/j5-ci.yml.
Merge Risk: 
Minimal · up to ec365
-
The CI timeout adjustment addresses reported shard cancellations without changing test behavior.
Pre-merge checks: 
4
-
Full details: Description check
-
Explanation
The description explains the problem, the timeout change, scope, testing status, checklist decisions, and authoring context. It omits the optional UI, live testing, and upstream impact sections because they are not applicable. It does not link a tracking issue, but the description is otherwise complete.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
Problem
J5 CI's server test shards keep hitting their 15-minute limit and are cancelled with no failing test. On 26 October that cancelled eleven shards across #660, #662, #663 and #664. On #660's last failure, the "Install Chromium" step took 11.5 of the 15 minutes, which left about four minutes for tests.
What changed
Raise
test_server'stimeout-minutesfrom 15 to 25 in.github/workflows/j5-ci.yml, with a comment saying why. No check, test or shard changes. Caching the Chromium install would be the longer-term fix. That is a separate concern and is not in this PR.Checklist
j5-ci.ymlis J5's own workflowMade with Claude Opus 5.5 in Claude Code (J5 Code). The local pre-commit hook was skipped because this worktree has no dependencies installed; CI's format check covers the change.
🤖 Generated with Claude Code