diff options
| author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2018-01-10 17:14:17 +0100 |
|---|---|---|
| committer | Adam J. Stewart <ajstewart426@gmail.com> | 2018-01-10 10:14:17 -0600 |
| commit | 596d463714d46929f81db62b171c5a772679bb12 (patch) | |
| tree | c6b15a9fcfc07af79db3cd686c391094146d6215 /.coveragerc | |
| parent | d17a10c6ac07f372bb27ef61b25edb0407c08b83 (diff) | |
| download | spack-596d463714d46929f81db62b171c5a772679bb12.tar.gz spack-596d463714d46929f81db62b171c5a772679bb12.tar.bz2 spack-596d463714d46929f81db62b171c5a772679bb12.tar.xz spack-596d463714d46929f81db62b171c5a772679bb12.zip | |
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.
Diffstat (limited to '.coveragerc')
| -rw-r--r-- | .coveragerc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/.coveragerc b/.coveragerc index 0201a4b502..224c472fa2 100644 --- a/.coveragerc +++ b/.coveragerc @@ -2,7 +2,6 @@ # .coveragerc to control coverage.py [run] parallel = True -concurrency = multiprocessing branch = True source = lib omit = |