Repository navigation
ci: Turbopack back on the self-hosted build slot (64 GB); webpack stays elsewhere - #16941
Merged
Merged
Conversation
…ys elsewhere The .113 build box was raised from 48 to 64 GB on 2026-10-16. Measured there with a cgroup cap and swap off, the Turbopack build of this tree peaks at ~36 GB under the cap (49 GB uncapped: compile ~21 GB plus 31 static-generation workers at 17-21 GB) and finished in 23 min with three lint jobs running alongside - no swap, no OOM, memory PSI 0. That is what did not fit the 48 GB box next to the light runners (~200 red Builds between 10-06 and 10-16). The ci.yml Build therefore goes back to Turbopack when it lands on the opt-in slot (USE_VPS_RUNNER and USE_VPS_BUILD_RUNNER both 'true') and keeps webpack on the 16 GB hosted runners, which cannot hold it. The four nightly build:cli steps stay on webpack: they are backend-only and share the box with the light runners. Next 16.4.x regresses (33 GB in the compile phase alone) and must be re-measured before any bump. Tests follow the policy: heavy-build-queue pins the Turbopack switch to the runner condition again, ci-build-bundler-webpack keeps the nightlies on webpack and checks the Build switch is tied to the slot.
Contributor
CI Coverage Report
Coverage artifact was not available for this run. PR Test PolicyThis PR changes production code in |
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
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.
Summary
ci.ymlBuildjob uses Turbopack again when it lands on the self-hosted build slot (USE_VPS_RUNNERandUSE_VPS_BUILD_RUNNERboth'true') and keeps webpack on hosted runners. Follow-up to ci: build with webpack in the nightlies and in the Build job (Turbopack OOMs the .113) #16870, which had forced webpack everywhere while the.113had 48 GB.build:clisteps stay on webpack (backend-only jobs that share the box with the light runners).tests/unit/build/heavy-build-queue.test.tspins the Turbopack switch to the runner condition again;tests/unit/ci-build-bundler-webpack.test.tskeeps the nightlies on webpack and checks that the Build switch is tied to the opt-in slot.Why
The
.113was raised from 48 to 64 GB on 2026-10-16 (VM drained runner by runner, no job killed). Validation on the box with the production tree (release/v3.8.52, Next 16.3.8, originalnext.config.mjs):experimental.cpus: 8next-buildalone reaches 33 GB in the compile phase - do not bump without re-measuringThe runner slot (
omniroute-113-5,MemoryHigh=42G/MemoryMax=45G) squeezes the build into the 36 GB range it tolerates. Worst case with the light runners at their own limits is still an overcommit of the 64 GB VM, so the first Builds are being watched;pve1-freeze-watchand the guest OOM log will show if the box needs more.Related Issues
Target Branch
release/v3.8.xbranch (the highest openrelease/v*), notmainValidation
heavy-build-queue.test.ts,ci-build-bundler-webpack.test.ts, plusvps-build-runner-gate,vps-runner-variable-scope,check-workflows-provenance-runner,quality-rail-gate-membership.113(artifact produced) before this changeTests Added Or Updated
tests/unit/build/heavy-build-queue.test.tsandtests/unit/ci-build-bundler-webpack.test.ts.Reviewer Notes
omniroute-113-5re-enabled, thenUSE_VPS_BUILD_RUNNER=true, then this merge - the push-triggered Build of the merge is the first real Turbopack run on the slot.omni-buildslot again (as before 10-16); fork PRs stay on hosted webpack.