<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/tools/concurrencytest, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2018-10-08T13:34:34Z</updated>
<entry>
<title>binman: Run tests concurrently</title>
<updated>2018-10-08T13:34:34Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2018-10-02T03:12:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=11ae93eef40c09280f36104b6a8cf5d807f0bb0d'/>
<id>urn:sha1:11ae93eef40c09280f36104b6a8cf5d807f0bb0d</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
