Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | concurrencytest: Fix Python3 warning | Simon Glass | 2021-01-05 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | This gives a warning in some situations: File "tools/dtoc/../concurrencytest/concurrencytest.py", line 95, in do_fork stream = os.fdopen(c2pread, 'rb', 1) File "/usr/lib/python3.8/os.py", line 1023, in fdopen return io.open(fd, *args, **kwargs) RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used Fix this by dropping the line-buffer parameter. Signed-off-by: Simon Glass <sjg@chromium.org> | ||||
* | tools: correct Markdown in concurrencytest/README.md | Heinrich Schuchardt | 2020-01-30 | 1 | -2/+2 |
| | | | | | | Remove incorrect indentation. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> | ||||
* | binman: Run tests concurrently | Simon Glass | 2018-10-08 | 3 | -0/+219 |
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> |