Eric Blake wrote: > On 04/02/2010 12:08 PM, Bruno Haible wrote: >> This ensures that long-running tests are executed last. So that the user >> gets the maximum of information as quickly as possible. > > That goes counter to the idea of parallel execution, where you want the > long-running tests front-loaded so that the shorter tests can fill in > the gaps. If the long-running tests are last, then the entire parallel > operation is stuck waiting for the last test. Is there any way this can > be made conditional, because there are good arguments for both orderings?
Seconded. I have deliberately reordered some tests to put long-running ones early enough so that a parallel (often -j5 or more) build completes as quickly as possible.
