2008/10/25 Daniel Berlin <[EMAIL PROTECTED]>: > I have placed a continuous builder (IE it does one build per svn > change) for GCC for x86_64 on an 8 core machine (nicely provided by > Google), and it has results here: > http://home.dberlin.org:8010/waterfall
I think this is great and pretty! Would it be possible to keep a list of the revisions that failed to build? That could be very useful for reg-hunting. Could the system send an email to the author of the revision that failed? > (I have not made it summarize the warnings yet, and these deliberately > do not run the testsuite in order to keep up with the repository. I > have more servers coming that will run builds that include running the > testsuite). Well, it seems idle right now. And with the new parallel testsuite, it shouldn't take so much time, so I think it could keep up with the repository. It seems just a waste of resources to build once and then build again somewhere else to run the testsuite. > In the next few days i will add a continuous builder for i686, as well > as a server that accepts patches for testing on these platforms and > spits back results in an hour or less, including the testsuite, so > those who want to test things while continuing work can do so. Great. Although this does not seem such an important issue given the existing Compile Farm. On the other hand, I seriously miss the patch tracker and I think I was not the only one and we have probably lost a few patches along the way. Any plans to bring it back? Cheers, Manuel.
