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

Failures in the "Build Windows Native Image" CI step #306

Closed
blickly opened this issue Apr 17, 2024 · 3 comments · Fixed by #307
Closed

Failures in the "Build Windows Native Image" CI step #306

blickly opened this issue Apr 17, 2024 · 3 comments · Fixed by #307
Assignees

Comments

@blickly
Copy link
Collaborator

blickly commented Apr 17, 2024

The last two CI runs (4 hours and 11 hours ago) have failed for the "Build Windows Native Image" step failed with the same error message:

 $ node build-image.js
  google-closure-compiler-windows building image
Error: spawn EINVAL
    at ChildProcess.spawn (node:internal/child_process:421:11)
    at spawn (node:child_process:761:9)
    at D:\a\closure-compiler-npm\closure-compiler-npm\build-scripts\run-command.js:53:23
    at new Promise (<anonymous>)
    at runCommand (D:\a\closure-compiler-npm\closure-compiler-npm\build-scripts\run-command.js:49:19)
    at Object.<anonymous> (D:\a\closure-compiler-npm\closure-compiler-npm\build-scripts\graal.js:60:1)
    at Module._compile (node:internal/modules/cjs/loader:1369:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1427:10)
    at Module.load (node:internal/modules/cjs/loader:1206:32)
    at Module._load (node:internal/modules/cjs/loader:1022:12) {
  errno: -4071,
  code: 'EINVAL',
  syscall: 'spawn'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.

It seems many of these CI steps are a bit flaky, so hopefully that's the case, but filing this issue to track just in case.

@blickly
Copy link
Collaborator Author

blickly commented Apr 19, 2024

Unfortunately, the looks to not be flaky, as there have now been a few more failures with the same message. Unfortunately, I don't think many on the team have the capacity to investigate (or a windows machine for that matter).

@ChadKillingsworth, do you have an idea what could be going wrong here?

@ChadKillingsworth
Copy link
Collaborator

I can definitely take a look. Diagnosing problems like this on windows builds is super challenging.

@ChadKillingsworth
Copy link
Collaborator

Oh this may be a security change by Node: https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2

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 a pull request may close this issue.

2 participants