-
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: do not run benchmark tests on 'make test' #34434
Conversation
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.
$(JS_SUITES) \ | ||
$(NATIVE_SUITES) |
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.
FWIW the reason we split tests into CI_JS_SUITES
and CI_NATIVE_SUITES
was that to accommodate the arm-fanned setup we split the tests into test-ci-native
(requires a build toolchain set up to build the native addons) and test-ci-js
(which "should not use a native compiler at all" (see comment in Makefile)).
For testing outside of the CI we don't have the same split in Makefile test targets, so you could optionally have a single make variable instead of two.
PR-URL: nodejs#34420 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Myles Borins <[email protected]>
CI: https://ci.nodejs.org/job/node-test-pull-request/32468/ This passed. |
PR-URL: nodejs#34048 Reviewed-By: Anna Henningsen <[email protected]>
Fixes: nodejs#34242 PR-URL: nodejs#34417 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]>
Otherwise the build would fail with `./configure --experimental-quic --ninja` as the list of per-Environment values would not match and the code cache builder would not generate code cache for the quic JS sources. This is more or less a band-aid - a proper fix would be to aggregate these flags into something that can be included by all these different binary targets. See nodejs#31074. PR-URL: nodejs#34454 Fixes: nodejs#34435 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Jiawen Geng <[email protected]>
This prevents accidental resource leaks when terminating or exiting Worker that own FDs opened through `fs.open()`. Refs: nodejs#34303 PR-URL: nodejs#34394 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
The "Labels" section of doc/guides/onboarding-extras.md was missing a reference to the `author-ready` label. This commit adds a description similar to the definition found in doc/guides/collaborator-guide.md with the goal of making it easier for new contributors to find labels info all in one place. PR-URL: nodejs#34381 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Myles Borins <[email protected]>
Notable changes: deps: * upgrade npm to 6.14.6 (claudiahdz) [nodejs#34246](nodejs#34246) * update node-inspect to v2.0.0 (Jan Krems) [nodejs#33447](nodejs#33447) * uvwasi: cherry-pick 9e75217 (Colin Ihrig) [nodejs#33521](nodejs#33521) PR-URL: nodejs#34343
Fixes: nodejs#34427 PR-URL: nodejs#34434 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Landed in 3caa2e2 |
Fixes: #34427 PR-URL: #34434 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Fixes: #34427 PR-URL: #34434 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Fixes: #34427 PR-URL: #34434 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Fixes: #34427 PR-URL: #34434 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Fixes: #34427 PR-URL: #34434 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Fixes: #34427 PR-URL: #34434 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Looks like we've been running benchmark tests locally with
make test
. Whoops. Let's not do that.Fixes: #34427
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes