[ci] Increase deploy test concurrency to 8 (#99770)
Increases test concurrency for the deploy test jobs to 8 (prev: 2 in the full suite, 1 in new build-and-test jobs). For deploy tests, the CPU-intensive work that should be as stable as possible (the Next.js build and server) does not happen on the runner. It happens remotely when the deployment is built at Vercel. The runner mostly handles I/O and setup: pushing the deployment, waiting for it to become ready, polling logs, and making requests against it. So the usual reason to cap concurrency (runner CPU contention) barely applies. Adjusted rate-limits: - 10x `api-projects-get` (prev failure: https://github.com/vercel/next.js/actions/runs/37617890690/job/112780953612#step:35:1159) Trade-offs to watch: - Peak concurrent Vercel deployments per run rises 4× (shards × 2 → shards × 8; 64 → 256 concurrent test files at today's shard counts). If we hit Vercel account deployment-concurrency limits, increase the limits - maybe we still need a bit beefier runners if the concurrent setup/tests starve runner CPU ## test plan - [x] [deploy tests with debug logging on this branch takes 30 minutes wall time without hitting Vercel rate limits](https://github.com/vercel/next.js/actions/runs/37627918534); usual flake on the 1st try (down from [97 minutes on canary](https://github.com/vercel/next.js/actions/runs/37588790388/attempts/1)) --------- Co-authored-by:Claude Code <noreply@anthropic.com>
Showing
Please
register
or
sign in
to comment