Travis: coverage: report check-themes with separate flag (#2570)

This makes sense in general (every check target should get its own
flag), and might help with tracking down unexpected coverage changes
(although those appear to be related to the C code only (gcov)).
This commit is contained in:
Daniel Hahler 2019-01-10 19:08:36 +01:00 committed by GitHub
parent b392e2ce74
commit 0acaaf6863
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions

View File

@ -187,8 +187,9 @@ script:
make check-unit || exit 1 make check-unit || exit 1
do_codecov unittests do_codecov unittests
make check-integration || exit 1 make check-integration || exit 1
make check-themes || exit 1
do_codecov functionaltests do_codecov functionaltests
make check-themes || exit 1
do_codecov themes
do_codecov_gcov c_code do_codecov_gcov c_code
travis_fold_end travis_fold_end