4d5061c3e3
It will default to 0, which means testr will automatically set it based on your CPU count. Allowing the user to set it with an environment variable lets them control the resources used and more easily debug any issues with tests impacting each other (by disabling concurrency). Change-Id: Ib8274d307991ac3c25180609cb015894f0bf52b3
11 lines
444 B
Plaintext
11 lines
444 B
Plaintext
[DEFAULT]
|
|
test_command=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
|
|
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
|
|
OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} \
|
|
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \
|
|
${PYTHON:-python} -m subunit.run discover -t ./ ./mistral/tests/unit $LISTOPT $IDOPTION
|
|
|
|
test_id_option=--load-list $IDFILE
|
|
test_list_option=--list
|
|
test_run_concurrency=echo ${TEST_RUN_CONCURRENCY:-0}
|