Travis: use --concurrency=multiprocessing only on build tests (#6872)
On a local workstation, it seems that tracking multiple processes during coverage may result in malformed coverage reports for unit tests and not for build tests. Given that multiple processes make a difference in coverage mainly for build tests, try to disable the tracking for unit tests to see if we get more stable coverage results.
This commit is contained in:
parent
d17a10c6ac
commit
596d463714
2 changed files with 5 additions and 2 deletions
|
@ -2,7 +2,6 @@
|
|||
# .coveragerc to control coverage.py
|
||||
[run]
|
||||
parallel = True
|
||||
concurrency = multiprocessing
|
||||
branch = True
|
||||
source = lib
|
||||
omit =
|
||||
|
|
|
@ -11,10 +11,14 @@ SPACK_ROOT="$QA_DIR/../../.."
|
|||
. "$SPACK_ROOT/share/spack/setup-env.sh"
|
||||
|
||||
# Set up some variables for running coverage tests.
|
||||
if [[ "$COVERAGE" == true ]]; then
|
||||
if [[ "$COVERAGE" == "true" && "$TEST_SUITE" == "unit" ]]; then
|
||||
coverage=coverage
|
||||
coverage_run="coverage run"
|
||||
coverage_combine="coverage combine"
|
||||
elif [[ "$COVERAGE" == "true" && "$TEST_SUITE" == "build" ]]; then
|
||||
coverage=coverage
|
||||
coverage_run="coverage run --concurrency=multiprocessing"
|
||||
coverage_combine="coverage combine"
|
||||
else
|
||||
coverage=""
|
||||
coverage_run=""
|
||||
|
|
Loading…
Reference in a new issue