On Monday, April 09, 2012 7:13:13 PM, Andrew Deason wrote:
> Or at least make them not fail the build. 'make check || true' perhaps > would not cause verification to fail, but we could still see what > happens when it runs. Who is going to look at the output? In the last two weeks we have twice hit the point where the slowest builders are so far behind the fastest builders that by the time the build reports finally get submitted to the coordinator none of the build logs are still available for the fastest builders. If the builders are not going to fail the build for a test failure I do not see the point of running them for every build as part of patchset verification. In my opinion what would be reasonable at this point would be to have a separate set of builders that run 'make check' on a daily basis. However, I do not want them in the current builder pool because failures that result in deadlock will bring the entire buildbot verification system to a halt. Jeffrey Altman
signature.asc
Description: OpenPGP digital signature
