Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.2k
build: run test-hash-seed at the end of test-v8#14219
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
refack commented Jul 13, 2017
Sounds right to me. IMHO |
ofrobots commented Jul 13, 2017
The original motivation was to make sure this gets run whenever we update V8 (i.e. the time we usually run test-v8 in the CI). IMO, |
ofrobots commented Jul 14, 2017
Perhaps something like: --- a/Makefile+++ b/Makefile@@ -433,13 +433,15 @@ test-async-hooks: ifneq ("","$(wildcard deps/v8/tools/run-tests.py)") -test-v8: v8 test-hash-seed+test-v8: v8 # note: performs full test unless QUICKCHECK is specified deps/v8/tools/run-tests.py --arch=$(V8_ARCH) \ --mode=$(BUILDTYPE_LOWER) $(V8_TEST_OPTIONS) $(QUICKCHECK_ARG) \ --no-presubmit \ --shell-dir=$(PWD)/deps/v8/out/$(V8_ARCH).$(BUILDTYPE_LOWER) \ $(TAP_V8) + @echo Testing hash seed+ $(MAKE) test-hash-seed |
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: nodejs#14004 (comment)
0b4a01e to fe8c222Comparetargos commented Jul 14, 2017
CI with that change: https://ci.nodejs.org/job/node-test-commit-v8-linux/783/ |
targos commented Jul 14, 2017
CI is green. Can we fast-track this fix to unbreak it? |
targos commented Jul 14, 2017
BTW I understood why test-hash-seed was there and it makes sense. I was reluctant because of the double V8 build but the job took only 30 minutes to run so that's fine. |
refack commented Jul 14, 2017
Just to be sure, spawning a sub-make propagates the exit code? |
targos commented Jul 14, 2017
@refack With this: test-a: test-b echo "test-a" $(MAKE) test-c test-b: echo "test-b" test-c: node -e "process.exit(1)" |
mhdawson left a comment
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.
The alternative is to make a new nightly job that just runs the hashseed test on its own. That would remove the overhead for those doing individual regression runs instead of the nightlies. We then might want to create better nightly job which runs both the hashseed and v8 test jobs.
In any case I'm +1 to landing this now to get the test back to green and the improve.
mhdawson commented Jul 14, 2017
I also think we should expedite landing this since the jobs are completely broken as they currently are. |
addaleax commented Jul 14, 2017 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Landed in 016d81c |
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: nodejs#14004 (comment) PR-URL: nodejs#14219 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: #14004 (comment) PR-URL: #14219 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: #14004 (comment) PR-URL: #14219 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: #14004 (comment) PR-URL: #14219 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: #14004 (comment) PR-URL: #14219 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: nodejs#14004 (comment) PR-URL: nodejs#14219 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: #14004 (comment) Backport-PR-URL: #15562 PR-URL: #14219 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
The v8 and test-hash-seed targets cannot be run in parallel because they need different copies of the deps/v8 directory. Ref: #14004 (comment) Backport-PR-URL: #15562 PR-URL: #14219 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
The v8 and test-hash-seed targets cannot be run in parallel because they
need different copies of the deps/v8 directory.
Ref: #14004 (comment)
I'm open to a better solution but I don't think
test-hash-seedshoud be run here, even if we make it sequential (V8 has to be built twice).@ofrobots @nodejs/v8
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes