Skip to content

fix(ci): Increase build application memory#4140

Merged
TheodoreSpeaks merged 1 commit intostagingfrom
fix/oom-ci
Apr 14, 2026
Merged

fix(ci): Increase build application memory#4140
TheodoreSpeaks merged 1 commit intostagingfrom
fix/oom-ci

Conversation

@TheodoreSpeaks
Copy link
Copy Markdown
Collaborator

Summary

We added some more dependencies causing build to fail. Increased memory to unblock build in ci.

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation
  • Other: ___________

Testing

  • Manually reviewed.

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 14, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Apr 14, 2026 0:23am

Request Review

@cursor
Copy link
Copy Markdown

cursor bot commented Apr 14, 2026

PR Summary

Low Risk
Low risk CI-only change that increases Node heap size to avoid out-of-memory failures during bun run test and turbo run build. No production code or runtime behavior is affected.

Overview
In the test-build GitHub Actions workflow, increases Node’s heap limit by appending --max-old-space-size=8192 to NODE_OPTIONS for the test and build steps, reducing CI failures from out-of-memory during heavier dependency builds.

Reviewed by Cursor Bugbot for commit 4eec739. Bugbot is set up for automated code reviews on this repo. Configure here.

@TheodoreSpeaks TheodoreSpeaks changed the title Increase build application memory fix(ci): Increase build application memory Apr 14, 2026
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 14, 2026

Greptile Summary

This PR bumps the Node.js heap limit to 8 GB (--max-old-space-size=8192) in two steps of the CI workflow — test-with-coverage and the Next.js build — to prevent out-of-memory failures introduced by recently added dependencies. The runner (blacksmith-8vcpu-ubuntu-2404) typically provides 16 GB RAM, so allocating 8 GB to Node.js is reasonable.

Confidence Score: 5/5

Safe to merge — minimal, targeted CI fix with no risk of regression.

Single-line change in two places, both well-scoped to the affected CI steps. The 8 GB limit is appropriate for an 8 vCPU / 16 GB RAM Blacksmith runner. No logic, application code, or tests are affected.

No files require special attention.

Important Files Changed

Filename Overview
.github/workflows/test-build.yml Adds --max-old-space-size=8192 to NODE_OPTIONS for both the test-with-coverage and build steps to prevent OOM failures in CI.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Checkout & Setup] --> B[Install Dependencies]
    B --> C[Validate Feature Flags]
    C --> D[Check Subblock ID Stability]
    D --> E[Lint Code]
    E --> F["Run Tests with Coverage\nNODE_OPTIONS: --no-warnings --max-old-space-size=8192"]
    F --> G[Check Schema & Migrations]
    G --> H["Build Application\nNODE_OPTIONS: --no-warnings --max-old-space-size=8192"]
    H --> I[Upload Coverage to Codecov]

    style F fill:#f9f,stroke:#333
    style H fill:#f9f,stroke:#333
Loading

Reviews (1): Last reviewed commit: "Increase build application memory" | Re-trigger Greptile

@TheodoreSpeaks TheodoreSpeaks merged commit 6587afb into staging Apr 14, 2026
14 checks passed
@TheodoreSpeaks TheodoreSpeaks deleted the fix/oom-ci branch April 14, 2026 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant