We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
node-main
Windows, https://ci.nodejs.org/job/node-test-binary-windows-js-suites/32232/RUN_SUBSET=3,nodes=win2022-COMPILED_BY-vs2022/testReport/junit/(root)/parallel/test_permission_dc_worker_threads/
No response
Running CI
Consistently
Test should not fail
https://ci.nodejs.org/job/node-test-binary-windows-js-suites/32232/RUN_SUBSET=3,nodes=win2022-COMPILED_BY-vs2022/testReport/junit/(root)/parallel/test_permission_dc_worker_threads/
--- duration_ms: 126.005 exitcode: 9 severity: fail stack: 'C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe: bad option: --experimental-permission' ...
The text was updated successfully, but these errors were encountered:
cc @RafaelGSS
Sorry, something went wrong.
You should rebase on main. It was fixed.
No branches or pull requests
Version
node-main
Platform
Subsystem
No response
What steps will reproduce the bug?
Running CI
How often does it reproduce? Is there a required condition?
Consistently
What is the expected behavior? Why is that the expected behavior?
Test should not fail
What do you see instead?
https://ci.nodejs.org/job/node-test-binary-windows-js-suites/32232/RUN_SUBSET=3,nodes=win2022-COMPILED_BY-vs2022/testReport/junit/(root)/parallel/test_permission_dc_worker_threads/
Additional information
No response
The text was updated successfully, but these errors were encountered: