Use --parallel-mode for test coverage
stestr runs in parallel, which is good, but coverage needs to run in parallel awareness mode, so that data from all stestr processes is collected. Closes-Bug: #2050838 Change-Id: I6a384f07d5063dc42b63943586d499f7647b1c64
This commit is contained in:
parent
610443f950
commit
caabd67022
@ -51,7 +51,7 @@ then
|
||||
# Run coverage on ops-sunbeam
|
||||
pushd ops-sunbeam
|
||||
coverage erase
|
||||
PYTHON="coverage run --omit .tox/*" stestr run --slowest || exit 1
|
||||
PYTHON="coverage run --parallel-mode --omit .tox/*" stestr run --slowest || exit 1
|
||||
coverage combine
|
||||
popd
|
||||
|
||||
@ -61,7 +61,7 @@ then
|
||||
push_common_files $charm || exit 1
|
||||
pushd charms/$charm
|
||||
coverage erase
|
||||
PYTHONPATH=./src:./lib:../../ops-sunbeam PYTHON="coverage run --omit .tox/*,src/templates/*" stestr run --slowest || exit 1
|
||||
PYTHONPATH=./src:./lib:../../ops-sunbeam PYTHON="coverage run --parallel-mode --omit .tox/*,src/templates/*" stestr run --slowest || exit 1
|
||||
coverage combine
|
||||
popd
|
||||
done
|
||||
|
Loading…
x
Reference in New Issue
Block a user