Repository navigation
fix(ci): webpack for docker-publish even on the 31 GB omni-build box - #12050
Merged
diegosouzapw merged 1 commit intoAug 29, 2026
Merged
Conversation
Turbopack had 31 GB on omniroute-113-6 and still panicked (TurbopackInternalError: there must be a path to a root, run 33253576569). The same tree's arm64 webpack build on hosted ARM succeeded. Dockerfile already documents webpack as the Docker escape hatch. Keep amd64 on the one omni-build slot (#12048).
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…ence#12050) Turbopack had 31 GB on omniroute-113-6 and still panicked (TurbopackInternalError: there must be a path to a root, run 33253576569). The same tree's arm64 webpack build on hosted ARM succeeded. Dockerfile already documents webpack as the Docker escape hatch. Keep amd64 on the one omni-build slot (cheaper-inference#12048).
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.
Why
#12021 moved docker-publish amd64 onto
.113(omniroute-113-6at the time). RAM was fine. The build still died after 26 min:Run: https://github.com/diegosouzapw/OmniRoute/actions/runs/33253576569
The same tree's arm64 webpack build on hosted
ubuntu-24.04-armsucceeded (run 33264823398). The Dockerfile already documentsOMNIROUTE_USE_TURBOPACK=0as the Docker escape hatch.Change
Hard-code
OMNIROUTE_USE_TURBOPACK=0on every docker-publish image (amd64 omni-build, arm64 hosted, bun legs). amd64 stays on the oneomni-buildslot (#12048).docs/ops/RUNNER_BOX.mdrecords docker-publish as a tenant of that slot.After merge, the next code push (or a dispatch) republishes
:next.Refs #11976 #12021 #12048