-
Notifications
You must be signed in to change notification settings - Fork 30k
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: add rule to clean addon tests build #11519
Conversation
yes please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. FWIW, there's another add-on in test/gc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the same functionality be added to vcbuild.bat
so Windows folks have it too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a++ Great work
LGTM
@bnoordhuis Oh yes, though I think that one should be @Trott +1 on the idea of adding this to vcbuild.bat, though I know so little about how to write one and I don't have Windows at the moment (technically one doesn't need Windows to consume it, but still), so I think better leave to another PR if anyone want to do it :) |
Hmm...I've tried to do a |
ARM failure is not a failure, as usual.. Landed in 813b312, thanks! |
Add a `test-addons-clean` to the Makefile to clean up files generated during testing addons. PR-URL: #11519 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>
Add a `test-addons-clean` to the Makefile to clean up files generated during testing addons. PR-URL: nodejs#11519 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>
Add a `test-addons-clean` to the Makefile to clean up files generated during testing addons. PR-URL: #11519 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>
Landed in in v6.x-staging. If it should land in v4.x-staging, please open a backport PR |
Depends on #10856 |
Add a `test-addons-clean` to the Makefile to clean up files generated during testing addons. PR-URL: #11519 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>
Add a rule to the makefile to clean up files generated during testing addons.
Note: when switching from a newer branch, where the addon tests have been built, to an older branch that don't have some of the addon tests, there would be leftover
build
directories in those test folders.test/addons/.buildstamp
would try to use node-gyp to build them, only to find thebinding.gyp
missing. If we run this rule before switching branches, there won't be leftoverbuild
and those test folders would not be kept when the branches are switched. I think thetest/addons/.buildstamp
can have some kind of conditions to avoid that or just delete folders with onlybuild
, but not sure what's the appropriate way to do this.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
build