diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2018-01-20 16:10:25 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-01-20 16:10:25 +0100 |
commit | 621388e5ae3e221a38372bbcf0e799b914f6dd27 (patch) | |
tree | f287867406499f4ff3ff89d56ea1ad7dfa695554 /share/spack/qa/run-unit-tests | |
parent | cf736ae9116314f01ab1ba9ca49bd6268fb28f61 (diff) | |
download | spack-621388e5ae3e221a38372bbcf0e799b914f6dd27.tar.gz spack-621388e5ae3e221a38372bbcf0e799b914f6dd27.tar.bz2 spack-621388e5ae3e221a38372bbcf0e799b914f6dd27.tar.xz spack-621388e5ae3e221a38372bbcf0e799b914f6dd27.zip |
Restore multiprocessing in unit tests (#6949)
* Revert "Travis: use --concurrency=multiprocessing only on build tests (#6872)"
This reverts commit 596d463714d46929f81db62b171c5a772679bb12.
* Removing 'coverage combine' in test script
According to what was discovered in #6887, one of the problems is
calling 'coverage combine' twice without the '-a' flag. This removes
the first call within our test scripts.
Diffstat (limited to 'share/spack/qa/run-unit-tests')
-rwxr-xr-x | share/spack/qa/run-unit-tests | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/share/spack/qa/run-unit-tests b/share/spack/qa/run-unit-tests index 87203ba915..74f92c19c5 100755 --- a/share/spack/qa/run-unit-tests +++ b/share/spack/qa/run-unit-tests @@ -29,4 +29,3 @@ ${coverage_run} bin/spack -p --lines 20 spec mpileaks # Run unit tests with code coverage ${coverage_run} bin/spack test "$@" -${coverage_combine} |