diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2018-01-11 03:41:19 +0100 |
---|---|---|
committer | Adam J. Stewart <ajstewart426@gmail.com> | 2018-01-10 20:41:19 -0600 |
commit | a4c4739626813ff207276e9804aa73dcca5ff3c6 (patch) | |
tree | 30d454d64d0fb9f872da48e05b5fb9e9b656a1f6 | |
parent | d07b83237daaee848f7750b7a70af0f7e86d0813 (diff) | |
download | spack-a4c4739626813ff207276e9804aa73dcca5ff3c6.tar.gz spack-a4c4739626813ff207276e9804aa73dcca5ff3c6.tar.bz2 spack-a4c4739626813ff207276e9804aa73dcca5ff3c6.tar.xz spack-a4c4739626813ff207276e9804aa73dcca5ff3c6.zip |
Travis: upload the coverage data as part of the script (#6877)
According to Travis docs the exit code of after_success doesn't affect
the build result. Instead, uploading the coverage data as the last step
of the script will cause the job to fail if the command exits with
non-zero.
https://docs.travis-ci.com/user/customizing-the-build/#Breaking-the-Build
-rw-r--r-- | .travis.yml | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/.travis.yml b/.travis.yml index 5b92f622b6..61b829a9c5 100644 --- a/.travis.yml +++ b/.travis.yml @@ -149,10 +149,9 @@ before_script: #============================================================================= # Building #============================================================================= -script: share/spack/qa/run-$TEST_SUITE-tests - -after_success: - - codecov --env PY_VERSION +script: + - share/spack/qa/run-$TEST_SUITE-tests + - if [[ "$COVERAGE" == "true" ]]; then codecov --env PY_VERSION --required ; fi #============================================================================= # Notifications |