fix(ci): sequential steps + single install to prevent OOM on runner #95

jason.woltje · 2026-03-13T18:10:38Z

jason.woltje commented

2026-03-13 18:10:38 +00:00

All quality steps (typecheck, lint, format, test) were running in parallel and each re-ran pnpm install. On merge commits with accumulated code this hit the runner OOM limit (exit 254).

Fix: install once, share workspace, sequential execution.

All quality steps (typecheck, lint, format, test) were running in parallel and each re-ran `pnpm install`. On merge commits with accumulated code this hit the runner OOM limit (exit 254). Fix: install once, share workspace, sequential execution.

jason.woltje added 1 commit 2026-03-13 18:10:39 +00:00

fix(ci): sequential steps + single install to prevent OOM on runner

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

c8f3e0db44

Each step was re-running pnpm install independently, and all quality
steps (typecheck, lint, format, test) ran in parallel. On merge commits
with more accumulated code this pushed the CI runner over its memory
limit (exit code 254 = OOM kill).

Fix:
- install once, share node_modules via Woodpecker workspace volume
- sequential execution: install → typecheck → lint → format → test → build
- corepack enable in each step (fresh container) but no redundant install

jason.woltje merged commit ab37c2e69f into main

2026-03-13 18:13:21 +00:00

jason.woltje referenced this issue from a commit

2026-03-13 18:13:23 +00:00

Merge pull request 'fix(ci): sequential steps + single install to prevent OOM on runner' (#95) from fix/ci-sequential into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaicstack/stack#95