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

Build is failing on Node.js 4 in production mode #3875

Closed
j-f1 opened this issue Feb 2, 2018 · 6 comments
Closed

Build is failing on Node.js 4 in production mode #3875

j-f1 opened this issue Feb 2, 2018 · 6 comments
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. type:infra Issues about CI, publishing to npm, or similar

Comments

@j-f1
Copy link
Member

j-f1 commented Feb 2, 2018

Several recent testing runs have failed because the Jest process gets “Killed:”

Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
/home/travis/build/prettier/prettier/node_modules/shelljs/src/common.js:417
      if (config.fatal) throw e;
                        ^
Error: exec: internal error
    at Object.error (/home/travis/build/prettier/prettier/node_modules/shelljs/src/common.js:128:27)
    at Object._exec (/home/travis/build/prettier/prettier/node_modules/shelljs/src/exec.js:292:12)
    at Object.exec (/home/travis/build/prettier/prettier/node_modules/shelljs/src/common.js:350:23)
    at Object.<anonymous> (/home/travis/build/prettier/prettier/scripts/test-dist.js:23:20)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:140:18)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

source

@j-f1 j-f1 added type:bug Issues identifying ugly output, or a defect in the program area:tests labels Feb 2, 2018
@alexander-akait
Copy link
Member

FYI: manually restart job fix this

@alexander-akait
Copy link
Member

alexander-akait commented Feb 2, 2018

Update to shellj@0.8.1 fixed this problem. See https://github.com/shelljs/shelljs/blob/master/CHANGELOG.md#v081-2018-01-20

Exec failing with internal error when piping large output shelljs/shelljs#818

EDIT (by @josephfrazier): Fix link to shelljs issue 818

@j-f1
Copy link
Member Author

j-f1 commented Feb 6, 2018

Looks like this still isn’t fixed.

@j-f1 j-f1 reopened this Feb 6, 2018
@alexander-akait
Copy link
Member

@j-f1 yep 😞

@azz azz added type:infra Issues about CI, publishing to npm, or similar and removed area:tests type:bug Issues identifying ugly output, or a defect in the program labels Feb 24, 2018
@alexander-akait
Copy link
Member

We drop node@4, so we can close this issue

@github-actions github-actions bot added the locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. label Jul 17, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. type:infra Issues about CI, publishing to npm, or similar
Projects
None yet
Development

No branches or pull requests

4 participants