On Thu, May 16, 2013 at 10:50:11PM +0200, Thomas Rast wrote:
One open issue with the last patch that currently eludes me: if I
combine --valgrind-parallel with any --valgrind=*, there are lots of
errors as (apparently) the valgrind wrapper setups race against each
other. However, without any
Peff and me discussed improving the usability of --valgrind testing.
In particular, two ideas that came up were options for running only a
subset of the tests in a file under --valgrind, and for running a
single test script under valgrind while exploiting parallelism.
So here's a little series.
2 matches
Mail list logo