Repository navigation
ci(elos): run tests with concurrency 2 on CI - #25
Conversation
Several test files start headless Chrome or an MCP server; full parallelism on small runners made Chrome miss its startup window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
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 |
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. |
The 10,000-event export/restore round-trip takes ~10 s locally but went past 60 s on CI runners. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Intermittent CI failures (headless Chrome not starting in time) appeared as more test files started Chrome or MCP servers in parallel. CI now runs
npm run test:ci(--test-concurrency=2); localnpm testunchanged.🤖 Generated with Claude Code