build: don't use lint-ci on Travis #27062
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
lint-ci
Makefile target differs fromlint
in that it writes toa 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 tolint
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), orvcbuild test
(Windows) passes