Repository navigation
perf(ci): bound parallel regression execution - #5558
Conversation
Part of #5495. Preserve the complete suite, dependency startup controls and package deadline while allowing eight already parallel test cases per package.
# Conflicts: # .github/workflows/ci.yaml
@codex review |
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. |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Blocker: none Cleared 2026-10-29: Runner repair #5559 merged at 0fd031e; the merge-group and actual merged-source browser runs, Validate Main, CodeQL and Code Quality all passed. Resume on that reviewed base and renew exact-head CI, independent review and readiness before protected queue entry. Previous record (historical): |
@coderabbitai full review |
✅ Action performed
|
|
No actionable comments were generated in the recent review.
|
Readiness at As the pipeline's user, I observed the complete hosted workflow and retained regression execution, plus the earlier 582-case/race validation of the unchanged authorization test inputs. The measured 407s-to-245s package result is scoped to that package; repository guards were the longest current CI job at 663s. Overall pipeline acceptance remains open on #5495. Live main is now |
Why
Slow independent validation delays platform delivery and recovery.
What
Use bounded concurrency for existing regression checks and run independent validation in two isolated groups, preserving every check and deadline. A matched local comparison improved the slowest suite from 407s to 245s; hosted feedback and total delivery time remain to be verified.
Part of #5495