Skip to content

tools: fix exit code when linting from CI #6412

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
wants to merge 1 commit into from

Conversation

mscdex
Copy link
Contributor

@mscdex mscdex commented Apr 27, 2016

Checklist
  • tests and code linting passes
  • the commit message follows commit guidelines
Affected core subsystem(s)
  • tools
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).

@mscdex mscdex added the tools Issues and PRs related to the tools directory. label Apr 27, 2016
@mscdex
Copy link
Contributor Author

mscdex commented Apr 27, 2016

/cc @jbergstroem

@Trott
Copy link
Member

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).
@mscdex mscdex force-pushed the tools-fix-jslint-ci-exit-code branch from 7052427 to c4d4423 Compare April 27, 2016 06:01
@mscdex
Copy link
Contributor Author

mscdex commented Apr 27, 2016

I've pushed some additional changes to exit early when a worker dies unexpectedly (e.g. in case of a SyntaxError or similar when eslint actually starts linting files inside a worker).

@phillipj
Copy link
Member

LGTM

2 similar comments
@jbergstroem
Copy link
Member

LGTM

@santigimeno
Copy link
Member

LGTM

@jasnell
Copy link
Member

jasnell commented Apr 28, 2016

CI: https://ci.nodejs.org/job/node-test-pull-request/2413/
LGTM if CI is green

@Trott
Copy link
Member

Trott commented Apr 28, 2016

@jasnell CI for this won't pass until #6411 lands (or changes are made to the CI linting VM).

@jasnell
Copy link
Member

jasnell commented Apr 28, 2016

thanks for the heads up. may want to indicate that in the PR description :-)

@Trott
Copy link
Member

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
Copy link
Member

Trott commented Apr 29, 2016

#6411 landed so this can be run in CI now.

Ci: https://ci.nodejs.org/job/node-test-pull-request/2427/

Trott pushed a commit to Trott/io.js that referenced this pull request Apr 29, 2016
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
Copy link
Member

Trott commented Apr 29, 2016

Landed in 1264cec

@Trott Trott closed this Apr 29, 2016
@mscdex mscdex deleted the tools-fix-jslint-ci-exit-code branch April 29, 2016 17:44
Fishrock123 pushed a commit that referenced this pull request May 4, 2016
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>
joelostrowski pushed a commit to joelostrowski/node that referenced this pull request May 4, 2016
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
Copy link
Contributor

@mscdex safe to assume this would be included with other linter changes if we were to backport?

@mscdex
Copy link
Contributor Author

mscdex commented Jun 1, 2016

@thealphanerd if by 'linter changes' you mean the addition of tools/jslint.js and PRs related to that, then yes.

@MylesBorins
Copy link
Contributor

that is what I mean

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants