> 15 cpus: > > [junit4] Slave 0: 0.29 .. 5.16 = 4.87s ... > [junit4] Slave 3: 0.29 .. 24.20 = 23.92s > [junit4] Slave 4: 0.26 .. 27.00 = 26.74s
This is weird -- such discrepancy shouldn't happen after it has some initial timings unless there was a really skewed test case inside. I do all per-vm suite balancing beforehand and don't adjust once the execution is in progress (probably using job stealing); maybe this is a mistake that should be corrected. Then the order of suites should be reported in case of a failure and if you have 20 slaves this would be a fairly large log ;) Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
