Skip to content
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: don't use lint-ci on Travis #27062

Merged
merged 1 commit into from
Apr 5, 2019
Merged

Conversation

richardlau
Copy link
Member

The lint-ci Makefile target differs from lint in that it writes to
a tap file and not stdout and also stops execution when an error is
found (e.g. if JavaScript linting fails the C++ and docs linting are
not run).

The switch to lint-ci was to enable Python linting. Revert to lint
and add the lint-py target.

Example Travis run where lint is used (note that C++ and docs linting occur after the JavaScript linter fails):
https://travis-ci.com/nodejs/node/jobs/189665652

Example Travis run where lint-ci is used (note that C++ and docs linting are not attempted after JavaScript linter fails and the actual linter failure is not visible):
https://travis-ci.com/nodejs/node/jobs/189720838

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot nodejs-github-bot added the build Issues and PRs related to build files or the CI. label Apr 2, 2019
@richardlau richardlau requested a review from refack April 2, 2019 22:38
@richardlau
Copy link
Member Author

If it was just the case of the linter failure not being visible we could echo the tap file in the after_failure Travis phase. I think it's more helpful though if all of the linters are run so you get all the failures in one go.

@BridgeAR BridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Apr 3, 2019
The `lint-ci` Makefile target differs from `lint` in that it writes to
a tap file and not stdout and also stops execution when an error is
found (e.g. if JavaScript linting fails the C++ and docs linting are
not run).

The switch to `lint-ci` was to enable Python linting. Revert to `lint`
and add the `lint-py` target.

PR-URL: nodejs#27062
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
@richardlau
Copy link
Member Author

Landed in af03de4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. build Issues and PRs related to build files or the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants