On Mon, Jun 10, 2013 at 12:33:30PM -0400, George Greer wrote: > At least for my Linux smokers, Benchmark.t test 15 fails not because > the clocks are inconsistent but because the load average can reach > over 100 at times depending on how many different smokes are > running, especially since they almost all do "make -j" and > TEST_JOBS=8. (The AddressSanitizer smokers don't use "make -j" > because I kernel panic'd my machine once doing that.) My machine > has 4 physical, 8 virtual cores so it doesn't blow the timings too > frequently but it does happen. > > A check for load average being "too high" after a failure to silence > it might help at least in my cases. Well, the test is failing fundamentally for one of two reasons: either the amount of CPU burned (as reported by the OS as (times)[0]) for a given amount of work is not constant, or there's a bug in Benchmark somewhere. If the former, whether its caused by high load or some other reason, I'm hoping my new change will detect this. -- That he said that that that that is is is debatable, is debatable.Thread Previous | Thread Next