Repository navigation
ci: serialize Fly deploys and cap turbo concurrency to stop OOM failures - #15
Merged
Merged
Conversation
The PR #14 merge exposed two resource-exhaustion failures that never hit PR runs: - Deploy: all three Fly apps built concurrently on the shared remote builder and api/match were OOM-killed (exit 137) in pnpm deploy. Serialize the matrix with max-parallel: 1. - CI: the lockfile change invalidated every turbo hash, so main ran all 25 tasks cold at default concurrency 10 and a vitest worker was killed. Cap the quality gate at --concurrency=4 to match runner cores. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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
The PR #14 merge produced two pipeline failures on main that never appeared on the PR itself — both resource exhaustion, not code bugs:
botswon the race;apiandmatchwere OOM-killed (exit code: 137) duringpnpm deploy --prod. First main deploy since the consolidated root Dockerfile put all three builds on one builder concurrently.Worker exited unexpectedly). The identical commit passed on the PR because the branch had warm caches.What
deploy.yml:max-parallel: 1on the deploy matrix — one app builds on the Fly builder at a time.ci.yml: quality gate runs with--concurrency=4— warm cached runs are unaffected; cold runs no longer stack multiple vitest/tsc/next-build processes.🤖 Generated with Claude Code