-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
tests: tools/node_modules is not present in tarball #51145
Comments
Seems this is kind of test regression introduced in #50684 where this tests relies on this removed tool. |
tools/node_modules is removed from the tarball so it should not be used as part of unit tests or benchmarks. Fixes: nodejs#51145
tools/node_modules is removed from the tarball so it should not be used as part of unit tests or benchmarks. Fixes: nodejs#51145 Refs: nodejs#50684
Ideally this should have been caught by the https://github.com/nodejs/node/blob/main/.github/workflows/build-tarball.yml workflow in #50684 but it was not 😞. |
this seems to copy things over 🤔 I think either these should be then shipped or should not be needed for tests? |
I'm not sure it's reasonable to expect that benchmarks and their tests work with the release tarball. |
Well, it's been working since at least nodejs 4.x 😉 I'm happy if The |
tools/node_modules is removed from the tarball so it should not be used as part of unit tests or benchmarks. Fixes: nodejs#51145 Refs: nodejs#50684
Version
No response
Platform
No response
Subsystem
No response
What steps will reproduce the bug?
No response
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
In git repository there is
https://github.com/nodejs/node/tree/main/tools/node_modules
in the source tarball, there is nothing there. This breaks at least
https://github.com/nodejs/node/blob/main/benchmark/misc/startup-cli-version.js#L13
Additional information
No response
The text was updated successfully, but these errors were encountered: