fix(ci): reduce Bazel jobs to 1 to prevent OOM crash - #207
Open
ricardochl wants to merge 1 commit into
Open
Conversation
ricardochl
changed the title
ricardochl
force-pushed
the
fix/ci-jobs-1-oom
branch
from
August 20, 2026 21:26
ab9945f to
4ab7842
Compare
adev-staging-deploy.yml failed on main with a genuine in-VM OOM signature (truncated log line + exit code 1) mid-compile at [17,472/17,628], distinct from the runner-shutdown flakiness seen in earlier runs. With --jobs=2, two concurrent Bazel actions (ng_package Rollup bundling, tsc compilation workers) can together exceed the runner's available memory even though --local_resources=memory=4096 is only a scheduling hint, not a hard cap. Serializing action execution with --jobs=1 avoids the concurrent memory spike without lowering the memory budget itself (which previously pushed build time to ~28min at memory=3072/jobs=2). Verified against both workflows: the PR check (ci.yml, run 32402548439, 28m25s) and a real push-triggered staging deploy including the Firebase deploy step (adev-staging-deploy.yml, run 32402468531, 4m9s) both completed successfully with this change.
ricardochl
force-pushed
the
fix/ci-jobs-1-oom
branch
from
August 20, 2026 21:44
4ab7842 to
b4da011
Compare
oidacra
approved these changes
Aug 20, 2026
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.
adev-staging-deploy.yml failed on main with a genuine in-VM OOM
signature (truncated log line + exit code 1) mid-compile at
[17,472/17,628], distinct from the runner-shutdown flakiness seen in
earlier runs. With --jobs=2, two concurrent Bazel actions (ng_package
Rollup bundling, tsc compilation workers) can together exceed the
runner's available memory even though --local_resources=memory=4096
is only a scheduling hint, not a hard cap.
Serializing action execution with --jobs=1 avoids the concurrent
memory spike without lowering the memory budget itself (which
previously pushed build time to ~28min at memory=3072/jobs=2).
Verified against both workflows: the PR check (ci.yml, run 32402548439,
28m25s) and a real push-triggered staging deploy including the
Firebase deploy step (adev-staging-deploy.yml, run 32402468531, 4m9s)
both completed successfully with this change.