u-boot.git/tools/concurrencytest, branch master Unnamed repository; edit this file 'description' to name the repository. concurrencytest: Fix Python3 warning 2021-01-05T19:26:35+00:00 Simon Glass sjg@chromium.org 2020-12-29T03:34:58+00:00 fe2400895ba0957b332926784daf21143f0f4835 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> 
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 2020-01-30T18:30:35+00:00 Heinrich Schuchardt xypron.glpk@gmx.de 2020-01-25T22:38:42+00:00 e4e355f6e456059aed4f9e4ea58eef636445e1d8 Remove incorrect indentation. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> 
Remove incorrect indentation.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
binman: Run tests concurrently 2018-10-08T13:34:34+00:00 Simon Glass sjg@chromium.org 2018-10-02T03:12:47+00:00 11ae93eef40c09280f36104b6a8cf5d807f0bb0d 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> 
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>