diff options
author | Paul Moore <paul@paul-moore.com> | 2018-05-10 16:59:49 -0400 |
---|---|---|
committer | Paul Moore <paul@paul-moore.com> | 2018-05-10 16:59:49 -0400 |
commit | 561c83cded2d91cd0ccc8e165af8fac45eed0fa3 (patch) | |
tree | aca2e5a4a230f31f9c14da7d943bcf386be5db8e | |
parent | 85cde70d0162c000dd4fc108b0ab0149c113c643 (diff) | |
download | libseccomp-561c83cded2d91cd0ccc8e165af8fac45eed0fa3.tar.gz |
travis: move the code coverage testing to the "after_success" stage
For an as yet unknown reason we keep seeing build failures due to the
code coverage tests despite there not being any noticeable failures.
Move the gcov testing to "after_success" so that failures won't mark
the build as failing.
Signed-off-by: Paul Moore <paul@paul-moore.com>
-rw-r--r-- | .travis.yml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/.travis.yml b/.travis.yml index 7e130d1..e96967e 100644 --- a/.travis.yml +++ b/.travis.yml @@ -61,10 +61,10 @@ script: - LIBSECCOMP_TSTCFG_TYPE=live make -C tests check # ubuntu 14.04 (trusty) clang has problems with the cython generated code - make clean && ./configure && scan-build --status-bugs make - # limit the code coverage tests to the 'test-code-coverage' target - - make clean && ./configure --enable-code-coverage && make test-code-coverage after_success: + # limit the code coverage tests to the 'test-code-coverage' target + - make clean && ./configure --enable-code-coverage && make test-code-coverage # https://github.com/eddyxu/cpp-coveralls/blob/master/README.md - coveralls --gcov-options '\-lp' --exclude tests --exclude tools --exclude src/arch-syscall-check.c |