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

Next-build: intercept failure of a worker thread and exit with status 1 #67154

Open
wants to merge 2 commits into
base: canary
Choose a base branch
from

Conversation

deh-code
Copy link

What?

If process run out of heap memory during next.js build process, it exits with error code 0, resulting in a "silent failure".

Why?

Looks like the build tasks are delegated to workers instantiated inside packages/next/src/build/webpack-build/index.ts

How?

Intercept failure of a worker and exit with code 1

Closes NEXT-
Fixes #67097

@ijjk
Copy link
Member

ijjk commented Jun 24, 2024

Allow CI Workflow Run

  • approve CI run for commit: c80aa5f

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

1 similar comment
@ijjk
Copy link
Member

ijjk commented Jun 24, 2024

Allow CI Workflow Run

  • approve CI run for commit: c80aa5f

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@ijjk
Copy link
Member

ijjk commented Jun 24, 2024

Allow CI Workflow Run

  • approve CI run for commit: 7c62308

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OOMKill is hidden during docker-based next build, build appears successful but isn't.
2 participants