| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Backported from 99bf6fa We can tell when `node-gyp` is changed by creating a prerequisite on `deps/npm/node_modules/node-gyp/package.json`. The prerequisite is added to the `test/addons/.buildstamp` since `build-addons` is .PHONY. Testing for this change was entirely manual. $ make clean test-build # Initial build $ make test-build # Make sure build-addons doesn't rebuild $ touch deps/npm/node_modules/node-gyp/package.json # simulate change $ make test-build # Ensure build-addons rebuilds Original PR-URL: #6787
|
CI: https://ci.nodejs.org/job/node-test-pull-request/3286/ Failed here, but it looks like it was a failure of git clean. I'm going to re-run, because this just seems flakey. Anyone seen this before? |
Sorry, something went wrong.
|
Successful CI: https://ci.nodejs.org/job/node-test-commit/4106/ |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
build
Description of change
Backported from
99bf6fa
We can tell when node-gyp is changed by creating a prerequisite on
deps/npm/node_modules/node-gyp/package.json. The prerequisite is added
to the test/addons/.buildstamp since build-addons is .PHONY.
Testing for this change was entirely manual.
$ make clean test-build # Initial build
$ make test-build # Make sure build-addons doesn't rebuild
$ touch deps/npm/node_modules/node-gyp/package.json # simulate change
$ make test-build # Ensure build-addons rebuilds
Original PR-URL: #6787