Repository navigation
[ci] Increase deploy test concurrency to 8 - #99770
Merged
Merged
Conversation
Contributor
Tests PassedCommit: 695f994 |
eps1lon
changed the title
eps1lon
force-pushed
the
sebbie/deploy-test-concurrency
branch
from
October 7, 2026 09:45
45d5f1a to
f8a56e4
Compare
eps1lon
changed the base branch from
canary
to
sebbie/deploy-timing-instrumentation
October 7, 2026 09:46
eps1lon
added this pull request to stack #99785
October 7, 2026 09:46
eps1lon
removed this pull request from stack #99785
October 7, 2026 10:02
eps1lon
force-pushed
the
sebbie/deploy-test-concurrency
branch
from
October 7, 2026 10:03
f8a56e4 to
44b1586
Compare
eps1lon
changed the base branch from
sebbie/deploy-timing-instrumentation
to
canary
October 7, 2026 10:03
eps1lon
force-pushed
the
sebbie/deploy-test-concurrency
branch
5 times, most recently
from
October 7, 2026 15:06
64a76ed to
a400601
Compare
Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
RUNNER_DEBUG=1 is set on re-runs with debug logging (matching @actions/core isDebug()), so vc --debug and its per-API-call status lines (including 429s) light up without a code change. Co-Authored-By: Claude Code <noreply@anthropic.com>
eps1lon
marked this pull request as ready for review
October 7, 2026 18:10
eps1lon
force-pushed
the
sebbie/deploy-test-concurrency
branch
from
October 7, 2026 18:10
a400601 to
695f994
Compare
eps1lon
enabled auto-merge (squash)
October 7, 2026 18:42
bgw
added a commit
that referenced
this pull request
Oct 8, 2026
Reverts #99770 We're seeing a lot of deployment test failures due to rate limits. We can try bumping the rate limits and trying again, but reverting for right now to unblock deployment tests.
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
2 participants
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.
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:
api-projects-get(prev failure: https://github.com/vercel/next.js/actions/runs/37617890690/job/112780953612#step:35:1159)Trade-offs to watch:
test plan