bors 8ac17731eb auto merge of #8531 : brson/rust/test-waitpid-workaround, r=graydon ... ...er I believe the calls to waitpid are interacting badly with the message passing that goes on between schedulers and causing us to have very little parallelism in the test suite. I don't fully understand the sequence of events that causes the problem here but clearly blocking on waitpid is something that a well-behaved task should not be doing. Unfortunately this adds quite a bit of overhead to each test: one thread, two tasks, three stacks, so there's a tradeoff. The time to execute run-pass on my 4-core machine goes from ~750s to ~300s. This should have a pretty good impact on cycle times. cc @toddaaro		2013-08-17 00:22:05 -07:00
..
common.rs	test: Fix tests.	2013-07-17 14:57:54 -07:00
compiletest.rs	core: option.map_consume -> option.map_move	2013-08-07 08:52:09 -07:00
errors.rs	test: Fix tests.	2013-07-17 14:57:54 -07:00
header.rs	std: Rename Iterator.transform -> .map	2013-08-10 07:33:21 -07:00
procsrv.rs	std: Change ProcessOptions struct to have an option of a ~ vector	2013-08-14 16:52:05 -07:00
runtest.rs	compiletest: Run tests in their own thread to avoid blocking the scheduler	2013-08-14 23:41:31 -07:00
util.rs	Bring compiletest/rustpkg/driver up to date on std vs core	2013-07-04 16:30:48 -07:00