On Friday, 20 June 2014 at 19:44:18 UTC, Steven Schveighoffer
wrote:
Timing individual tests is more likely to be accurate than
timing the whole set of unit tests. A slow machine could easily
double or triple the time the whole thing takes, and it would
be difficult to pinpoint a reasonable time that all machines
would accept.
That's true if you expect the timeout to be hit as part of
regular testing. If it's only to keep the auto tester from
hanging, just setting a one-minute global timeout per test case
(or something like that) should be fine. Sure, the auto-tester
throughput would suffer somewhat as long as the build is broken,
but…
David
