Skip to content

test: run the addon tests last - #12062

Closed
seppevs wants to merge 1 commit into
nodejs:masterfrom
seppevs:test_run_addon_tests_last
Closed

test: run the addon tests last#12062
seppevs wants to merge 1 commit into
nodejs:masterfrom
seppevs:test_run_addon_tests_last

Conversation

@seppevs

Copy link
Copy Markdown
Contributor

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), or vcbuild test (Windows) passes
  • commit message follows [commit guidelines][]
Affected core subsystem(s)

test

@nodejs-github-botnodejs-github-bot added the build Issues and PRs related to build files or the CI. label Mar 27, 2017
@aqrln

aqrln commented Mar 27, 2017

Copy link
Copy Markdown
Contributor

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 ?).

@seppevs
seppevsforce-pushed the test_run_addon_tests_last branch from 9eeb691 to cb369d2CompareMarch 27, 2017 10:42
@seppevs

Copy link
Copy Markdown
ContributorAuthor

Thanks for the tips, I've changed the commit message.

@seppevsseppevs changed the title test: run the addon tests laststest: run the addon tests lastMar 27, 2017
@vsemozhetbyt

vsemozhetbyt commented Mar 27, 2017

Copy link
Copy Markdown
Contributor

@vsemozhetbyt

vsemozhetbyt commented Mar 27, 2017

Copy link
Copy Markdown
Contributor

Does this affect Windows builds? Should the vcbuild.bat also be fixed?

@vsemozhetbyt

Copy link
Copy Markdown
Contributor

Some tests failed, trying another CI: https://ci.nodejs.org/job/node-test-pull-request/7055/

@aqrln

Copy link
Copy Markdown
Contributor

@aqrln

Copy link
Copy Markdown
Contributor

@vsemozhetbyt those tests are unrelated to this PR and I don't think another CI run will help, tbh :)
Failed test on Windows is already marked as flaky in #12054, and I've seen parallel/test-async-wrap-check-providers as well as other tests failing with timeout on CentOS 5 for a while too (just open any of the recent PRs).

@seppevs
seppevsforce-pushed the test_run_addon_tests_last branch from cb369d2 to dc3a770CompareMarch 27, 2017 13:45
@seppevs

Copy link
Copy Markdown
ContributorAuthor

@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).

@aqrln

aqrln commented Mar 27, 2017

Copy link
Copy Markdown
Contributor

@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

Copy link
Copy Markdown
Contributor

/cc @nodejs/build @nodejs/platform-windows

@Fishrock123Fishrock123 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please.

cc @bnoordhuis probably?

Comment threadMakefile Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One more thing. CI runs make test-ci, not make test, so you need to change line 311 too.

@seppevsseppevsMar 27, 2017

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I've changed the order on line 311 as well.

@seppevs
seppevsforce-pushed the test_run_addon_tests_last branch from dc3a770 to 3196f56CompareMarch 27, 2017 14:37

@jasnelljasnell left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that failures in cctest also suffer this problem.

@mscdexmscdex added addons Issues and PRs related to native addons. test Issues and PRs related to the tests. labels Mar 27, 2017
@refack

Copy link
Copy Markdown
Contributor

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).

So on windows, it's only a half solution since build-addons is run before the tests, and so it the build fails no tests are run 😞

@aqrln

Copy link
Copy Markdown
Contributor

@refack hmm, not only only on Windows. The same goes for Unix.

Comment threadMakefile Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe split this to "all other test" -> build -> "test addons"... 🤔

Comment threadvcbuild.bat Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is you decide to split the test, you'll need it here too...

@refackrefack left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Too much hassle to refactor vcbuild.bat
Current LGTM (works on Windows)

@seppevs
seppevsforce-pushed the test_run_addon_tests_last branch from 3196f56 to 141a6d9CompareApril 4, 2017 10:23
@jasnell

Copy link
Copy Markdown
Member

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
@seppevs
seppevsforce-pushed the test_run_addon_tests_last branch from 141a6d9 to 9149610CompareApril 4, 2017 20:38
@seppevs

Copy link
Copy Markdown
ContributorAuthor

@jasnell rebase done

@mscdex

Copy link
Copy Markdown
Contributor

@aqrln

Copy link
Copy Markdown
Contributor

@seppevs can you please rebase it again?

@jasnell

jasnell commented Apr 13, 2017

Copy link
Copy Markdown
Member

This needs to be rebased before it can land! :-)

ha! posted then saw @aqrln's comment. guess I should read all the way through before posting ;-)

@refack

Copy link
Copy Markdown
Contributor

Poor guy already rebased one. I'm taking care of this.

refack pushed a commit to refack/node that referenced this pull request Apr 13, 2017
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>
@refackrefack closed this Apr 13, 2017
@refack

Copy link
Copy Markdown
Contributor

Landed in 3d2181c

@jasnelljasnell mentioned this pull request May 11, 2017
@gibfahngibfahn mentioned this pull request Jun 15, 2017
3 tasks
gibfahn pushed a commit that referenced this pull request Jun 18, 2017
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>
gibfahn pushed a commit that referenced this pull request Jun 20, 2017
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>
MylesBorins pushed a commit that referenced this pull request Jul 11, 2017
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>
@MylesBorinsMylesBorins mentioned this pull request Jul 18, 2017
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

addonsIssues and PRs related to native addons.buildIssues and PRs related to build files or the CI.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

12 participants

@seppevs@aqrln@vsemozhetbyt@refack@jasnell@mscdex@bnoordhuis@Fishrock123@cjihrig@richardlau@gibfahn@nodejs-github-bot