-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Conversation
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py
On a few of our installations (namely CentOS), passing 'INFO' resulted in a silent loglevel. Use a logging constant instead. Cherry-picked from nodejs/node@8606793 Original commit metadata follows: Fixes: nodejs/build#104 PR-URL: nodejs/node#1842 Reviewed-By: Rod Vagg <[email protected]>
@@ -81,7 +84,6 @@ goto next-arg | |||
|
|||
:args-done | |||
if defined upload goto upload | |||
if defined jslint goto jslint |
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.
Does vcbuild jslint
still work? It seems that with this change it would only work when tests are run too.
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.
Good catch. This change enables building and testing, when jslint is specified. But it has the side effect of not getting to jslint unless you run tests. Will fix.
Thank you @orangemocha! Added a few comments. |
Adding support for specifying flaky test mode to the test runner: - via an environment variable FLAKY_TESTS for Makefile - via an argument ignore-flaky for vcbuild.bat Conflicts: Makefile
Make the test runner return a 0 exit code when only flaky tests fail and --flaky-tests=dontcare is specified.
Adding a single rule to be called from Jenkins.
Updated to fix extra line and jslint issue. Sneak preview CI run: https://jenkins-iojs.nodesource.com/job/orangemocha-test-commit/4/ |
LGTM. That's great! Do we plan to backport this to v0.10 too and test + build v0.10 releases from the converged CI? |
I might give it a shot, but given that we currently don't use node-accept-pull-request for v0.10, I will probably settle for just porting the current workflow, and then work on enabling node-accept-pull-request on v0.10 later. What job do you currently use on v0.10, BTW? Thanks for reviewing! |
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py Reviewed-By: Julien Gilli <[email protected]> PR-URL: #25653
On a few of our installations (namely CentOS), passing 'INFO' resulted in a silent loglevel. Use a logging constant instead. Cherry-picked from nodejs/node@8606793 Original commit metadata follows: Fixes: nodejs/build#104 PR-URL: nodejs/node#1842 Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Julien Gilli <[email protected]> PR-URL: #25653
Reviewed-By: Julien Gilli <[email protected]> PR-URL: #25653
Adding support for specifying flaky test mode to the test runner: - via an environment variable FLAKY_TESTS for Makefile - via an argument ignore-flaky for vcbuild.bat Conflicts: Makefile Reviewed-By: Julien Gilli <[email protected]> PR-URL: #25653
Make the test runner return a 0 exit code when only flaky tests fail and --flaky-tests=dontcare is specified. Reviewed-By: Julien Gilli <[email protected]> PR-URL: #25653
Adding a single rule to be called from Jenkins. Reviewed-By: Julien Gilli <[email protected]> PR-URL: #25653
Landed in c9ef4b3. |
@orangemocha Sounds good! Currently we use the |
This is a minimal effort to support test output written both to stdout and file in order to get our buildbots understanding test output. Cherry picked from jbergstroem/node@3194073 Original commit message follows: PR-URL: nodejs/node#934 Reviewed-By: Chris Dickinson <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Conflicts: tools/test.py Reviewed-By: Julien Gilli <[email protected]> PR-URL: nodejs#25653
On a few of our installations (namely CentOS), passing 'INFO' resulted in a silent loglevel. Use a logging constant instead. Cherry-picked from nodejs/node@8606793 Original commit metadata follows: Fixes: nodejs/build#104 PR-URL: nodejs/node#1842 Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Julien Gilli <[email protected]> PR-URL: nodejs#25653
Reviewed-By: Julien Gilli <[email protected]> PR-URL: nodejs#25653
Adding support for specifying flaky test mode to the test runner: - via an environment variable FLAKY_TESTS for Makefile - via an argument ignore-flaky for vcbuild.bat Conflicts: Makefile Reviewed-By: Julien Gilli <[email protected]> PR-URL: nodejs#25653
Make the test runner return a 0 exit code when only flaky tests fail and --flaky-tests=dontcare is specified. Reviewed-By: Julien Gilli <[email protected]> PR-URL: nodejs#25653
Adding a single rule to be called from Jenkins. Reviewed-By: Julien Gilli <[email protected]> PR-URL: nodejs#25653
..continued from #25541
As part of CI reconciliation, these commits make v0.12 work with the jobs at https://jenkins-iojs.nodesource.com/
This PR addresses all review feedback from #25541. In particular: