Uh oh!
There was an error while loading. Please reload this page.
tools: fix exit code when linting from CI - #6412
Conversation
mscdex
commented
Apr 27, 2016
/cc @jbergstroem |
Trott
commented
Apr 27, 2016
This probably should only land after #6411 lands or the CI lint VM is updated to Node.js 6.0.0. |
Before this, if there were lint errors reported by `make jslint-ci`, the process would still exit with an exit code of zero. This commit fixes that to align with `make jslint` (exit with non-zero on lint errors).
7052427 to
c4d4423Comparemscdex
commented
Apr 27, 2016
I've pushed some additional changes to exit early when a worker dies unexpectedly (e.g. in case of a |
phillipj
commented
Apr 27, 2016
LGTM |
2 similar comments
jbergstroem
commented
Apr 27, 2016
LGTM |
santigimeno
commented
Apr 28, 2016
LGTM |
jasnell
commented
Apr 28, 2016
CI: https://ci.nodejs.org/job/node-test-pull-request/2413/ |
Trott
commented
Apr 28, 2016
jasnell
commented
Apr 28, 2016
thanks for the heads up. may want to indicate that in the PR description :-) |
Trott
commented
Apr 28, 2016
@jasnell Additional complication is that requirement is only true on master. v4.x can get this PR right now and it will be just fine. |
Trott
commented
Apr 29, 2016
#6411 landed so this can be run in CI now. |
Before this, if there were lint errors reported by `make jslint-ci`, the process would still exit with an exit code of zero. This commit fixes that to align with `make jslint` (exit with non-zero on lint errors). PR-URL: nodejs#6412 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Phillip Johnsen <johphi@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Trott
commented
Apr 29, 2016
Landed in 1264cec |
Before this, if there were lint errors reported by `make jslint-ci`, the process would still exit with an exit code of zero. This commit fixes that to align with `make jslint` (exit with non-zero on lint errors). PR-URL: #6412 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Phillip Johnsen <johphi@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Before this, if there were lint errors reported by `make jslint-ci`, the process would still exit with an exit code of zero. This commit fixes that to align with `make jslint` (exit with non-zero on lint errors). PR-URL: nodejs#6412 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Phillip Johnsen <johphi@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
MylesBorins
commented
Jun 1, 2016
@mscdex safe to assume this would be included with other linter changes if we were to backport? |
mscdex
commented
Jun 1, 2016
@thealphanerd if by 'linter changes' you mean the addition of |
MylesBorins
commented
Jun 2, 2016
that is what I mean |
Checklist
Affected core subsystem(s)
Description of change
Before this, if there were lint errors reported by
make jslint-ci, the process would still exit with an exit code of zero.This commit fixes that to align with
make jslint(exit with code 1 on lint errors).