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

Linter failure details not shown on Travis? #21263

Closed
richardlau opened this issue Jun 11, 2018 · 4 comments
Closed

Linter failure details not shown on Travis? #21263

richardlau opened this issue Jun 11, 2018 · 4 comments

Comments

@richardlau
Copy link
Member

Has anyone seen the Travis linter job fail? Did it report the actual failure?

Looking at nodejs/build#720 it doesn't look like that tap file is echoed in the Travis config so even if the job fails the failure details are not reported:

node/.travis.yml

Lines 1 to 24 in fa2d0a1

language: cpp
compiler:
- clang
sudo: false
cache: ccache
matrix:
include:
- os: linux
node_js: "latest"
script:
- NODE=$(which node) make lint-ci
- os: linux
install:
- ./configure
- make -j2 V=
script:
- make -j2 test-ci
before_install:
- export HOMEBREW_NO_AUTO_UPDATE=1 # work around https://github.com/travis-ci/travis-ci/issues/7456
- if [ $TRAVIS_OS_NAME = osx ]; then brew install ccache; fi
- export PATH="/usr/local/opt/ccache/libexec:$PATH"
- export CXX="ccache clang++ -Qunused-arguments"
- export CC="ccache clang -Qunused-arguments"
- export JOBS=2

@richardlau
Copy link
Member Author

Here's an example failing Travis linter run, https://travis-ci.com/nodejs/node/jobs/128902170:

$ NODE=$(which node) make lint-ci
Running JS linter...
make: *** [lint-js-ci] Error 1


The command "NODE=$(which node) make lint-ci" exited with 2.

So as suspected the details of the failure aren't shown making this less helpful.

@Trott
Copy link
Member

Trott commented Jun 12, 2018

Any idea if changing it to make lint would cause it to show the output? I wonder if the problem is stuff being swallowed by the tools/lint.js script.

@lundibundi
Copy link
Member

@Trott not sure but maybe it's due to redirecting linter output to a file for ci target?

run-lint-js-ci = tools/lint-js.js $(PARALLEL_ARGS) -f tap -o test-eslint.tap \
		$(LINT_JS_TARGETS)

And Travis doesn't seem to be configured to read that file if the job fails like Jenkins does (latest build action).

@richardlau
Copy link
Member Author

Fixed by #22417.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants