Uh oh!
There was an error while loading. Please reload this page.
test: run the addon tests last - #12062
Conversation
I think that "See ..." line should be formatted as a proper "Refs:" or "Fixes:" metadata field. Also, there's probably a typo in the commit message (s/lasts/last ?). |
9eeb691 to
cb369d2Compareseppevs
commented
Mar 27, 2017
Thanks for the tips, I've changed the commit message. |
Does this affect Windows builds? Should the |
vsemozhetbyt
commented
Mar 27, 2017
Some tests failed, trying another CI: https://ci.nodejs.org/job/node-test-pull-request/7055/ |
aqrln
commented
Mar 27, 2017
@seppevs regarding @vsemozhetbyt's comment, please see https://github.com/nodejs/node/blob/master/vcbuild.bat#L62-L63. |
aqrln
commented
Mar 27, 2017
@vsemozhetbyt those tests are unrelated to this PR and I don't think another CI run will help, tbh :) |
cb369d2 to
dc3a770Compareseppevs
commented
Mar 27, 2017
@aqrln Thanks for the tip. I have modified the vcbuild.bat now. Can you review it, I'm not completely sure I did it correctly (and I have no Windows machine to verify). |
@seppevs heh, neither do I, so I hope my suggestion was correct :) /cc @nodejs/build @nodejs/platform-windows EDIT: whoops, only members can mention teams. @vsemozhetbyt can you do that, please? |
vsemozhetbyt
commented
Mar 27, 2017
/cc @nodejs/build @nodejs/platform-windows |
Fishrock123
left a comment
There was a problem hiding this comment.
Yes please.
cc @bnoordhuis probably?
dc3a770 to
3196f56Compare
jasnell
left a comment
There was a problem hiding this comment.
Note that failures in cctest also suffer this problem.
refack
commented
Mar 29, 2017
So on windows, it's only a half solution since |
aqrln
commented
Mar 29, 2017
@refack hmm, not only only on Windows. The same goes for Unix. |
There was a problem hiding this comment.
maybe split this to "all other test" -> build -> "test addons"... 🤔
There was a problem hiding this comment.
Is you decide to split the test, you'll need it here too...
refack
left a comment
There was a problem hiding this comment.
Too much hassle to refactor vcbuild.bat
Current LGTM (works on Windows)
3196f56 to
141a6d9Comparejasnell
commented
Apr 4, 2017
This needs a rebase before it can be landed. |
Running the addon tests before the parallel, sequential, etc. tests can be a problem if there is a bug in node that prevents the addon tests from running properly. When the addon tests fail for any reason, then none of the other tests (e.g. parallel, etc.) are executed. Running the addon tests last fixes this. Refs: nodejs#12031
141a6d9 to
9149610Compareseppevs
commented
Apr 4, 2017
@jasnell rebase done |
mscdex
commented
Apr 5, 2017
aqrln
commented
Apr 12, 2017
@seppevs can you please rebase it again? |
ha! posted then saw @aqrln's comment. guess I should read all the way through before posting ;-) |
refack
commented
Apr 13, 2017
Poor guy already rebased one. I'm taking care of this. |
Running the addon tests before the parallel, sequential, etc. tests can be a problem if there is a bug in node that prevents the addon tests from running properly. When the addon tests fail for any reason, then none of the other tests (e.g. parallel, etc.) are executed. Running the addon tests last fixes this. Refs: nodejs#12031 PR-URL: nodejs#12062 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
refack
commented
Apr 13, 2017
Landed in 3d2181c |
Running the addon tests before the parallel, sequential, etc. tests can be a problem if there is a bug in node that prevents the addon tests from running properly. When the addon tests fail for any reason, then none of the other tests (e.g. parallel, etc.) are executed. Running the addon tests last fixes this. Refs: #12031 PR-URL: #12062 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Running the addon tests before the parallel, sequential, etc. tests can be a problem if there is a bug in node that prevents the addon tests from running properly. When the addon tests fail for any reason, then none of the other tests (e.g. parallel, etc.) are executed. Running the addon tests last fixes this. Refs: #12031 PR-URL: #12062 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Running the addon tests before the parallel, sequential, etc. tests can be a problem if there is a bug in node that prevents the addon tests from running properly. When the addon tests fail for any reason, then none of the other tests (e.g. parallel, etc.) are executed. Running the addon tests last fixes this. Refs: #12031 PR-URL: #12062 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Running the addon tests before the parallel, sequential, etc. tests
can be a problem if there is a bug in node that prevents the
addon tests from running properly. When the addon tests fail for any
reason, then none of the other tests (e.g. parallel, etc.)
are executed.
Running the addon tests last fixes this.
See #12031
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
test