diff options
| author | Simon Glass <sjg@chromium.org> | 2018-10-01 21:12:47 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2018-10-08 07:34:34 -0600 |
| commit | 11ae93eef40c09280f36104b6a8cf5d807f0bb0d (patch) | |
| tree | 66b0e782d4901eb24e87354444bb73dda4f39a0e /tools/patman | |
| parent | 2673afe221d17b8d43df3ecae3e3a6024b209ffe (diff) | |
| download | u-boot-11ae93eef40c09280f36104b6a8cf5d807f0bb0d.tar.gz | |
binman: Run tests concurrently
At present the tests run one after the other using a single CPU. This is
not very efficient. Bring in the concurrencytest module and run the tests
concurrently, using one process for each CPU by default. A -P option
allows this to be overridden, which is necessary for code-coverage to
function correctly.
This requires fixing a few tests which are currently not fully
independent.
At some point we might consider doing this across all pytests in U-Boot.
There is a pytest version that supports specifying the number of processes
to use, but it did not work for me.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/patman')
| -rw-r--r-- | tools/patman/test_util.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/patman/test_util.py b/tools/patman/test_util.py index 0e79af871ab..687d40704ab 100644 --- a/tools/patman/test_util.py +++ b/tools/patman/test_util.py @@ -43,7 +43,7 @@ def RunTestCoverage(prog, filter_fname, exclude_list, build_dir, required=None): glob_list += exclude_list glob_list += ['*libfdt.py', '*site-packages*'] cmd = ('PYTHONPATH=$PYTHONPATH:%s/sandbox_spl/tools python-coverage run ' - '--omit "%s" %s -t' % (build_dir, ','.join(glob_list), prog)) + '--omit "%s" %s -P1 -t' % (build_dir, ','.join(glob_list), prog)) os.system(cmd) stdout = command.Output('python-coverage', 'report') lines = stdout.splitlines() |