mozilla/rust — Issue #1921: On non-compiletest tests, only use a single test task when valgrinding
Author: brson
Created: 2012-03-04 00:12:00+00:00
State: open
Labels: A-build, A-testsuite, E-easy, I-slow

For test runners that don't spawn subprocesses for every test (rustc, core, std, rustdoc), trying to run tests in parallel under valgrind just makes the entire test run slower. The build should detect when we are valgrinding and pass a flag (that doesn't exist yet) to the test runner telling it to use only 1 test task at a time.

I've noticed that the linux1 bot is taking an absurd amount of time to run coretest. This might help.