Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase --max-old-space-size option for 2.21 #195

Merged
merged 2 commits into from
Apr 28, 2024

Conversation

huonw
Copy link
Contributor

@huonw huonw commented Apr 27, 2024

It appears that we need more memory to build after branching for 2.21: the update that splits it (#193) is failing due to running out of memory.

This bumps to 12GiB, slightly less than the runner's RAM (16GB).

(#196 validates that this does actually fix it for 2.21.)

@huonw huonw marked this pull request as ready for review April 27, 2024 08:30
@huonw huonw requested review from thejcannon and kaos April 27, 2024 08:32
@@ -44,7 +44,7 @@ jobs:
- name: Build
run: npm run build
env:
NODE_OPTIONS: --max-old-space-size=6144
NODE_OPTIONS: --max-old-space-size=8192
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the max for our runner? Might as well just jump to something near that?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, it looks like the runners have 16GB RAM. I'll bump this up to 12288.

@huonw huonw enabled auto-merge (squash) April 27, 2024 23:47
@huonw huonw merged commit d3b2f41 into pantsbuild:main Apr 28, 2024
1 check passed
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.

2 participants