be995bcf80
Full support for parallel testr workers now works in keystone. The major item to be aware of is that if non-SQLite backends or a LIVE LDAP backend is being used for testing, the concurrency must be set to 1 to avoid conflicts. To artificially set the concurrency set the env variable ``TEST_RUN_CONCURRENCY`` to the desired number of testr workers. The default is to run one worker. To use 1 per available core, set ``TEST_RUN_CONCURRENCY`` to 0. Each worker uses a subdirectory of the test temp dir based upon the PID. When the worker exists (via the use of atexit), the worker-specific PID directory is automatically removed. The first time concurrent tests are run in a given environment, ensure that old .testrepository directories are cleaned up as they may introduce bad learning data on how to bin the tests based upon test runs that occured without concurrency. Closes-Bug: #1240052 Change-Id: I5c3385a431774ce574266a82065ed6237e8b3665
18 lines
628 B
Plaintext
18 lines
628 B
Plaintext
[DEFAULT]
|
|
test_command=${PYTHON:-python} -m subunit.run discover \
|
|
-t ./ ./keystone/tests \
|
|
$LISTOPT $IDOPTION
|
|
|
|
test_id_option=--load-list $IDFILE
|
|
test_list_option=--list
|
|
group_regex=.*(test_cert_setup|test_keystoneclient).+
|
|
|
|
|
|
# NOTE(morganfainberg): If single-worker mode is wanted (e.g. for live tests)
|
|
# the environment variable ``TEST_RUN_CONCURRENCY`` should be set to ``1``. If
|
|
# a non-default (1 worker per available core) concurrency is desired, set
|
|
# environment variable ``TEST_RUN_CONCURRENCY`` to the desired number of
|
|
# workers.
|
|
test_run_concurrency=echo ${TEST_RUN_CONCURRENCY:-1}
|
|
|