<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 16, 2009, at 12:04 PM, Daniel Dunbar wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>2009/7/15 Török Edwin <<a href="mailto:edwintorok@gmail.com">edwintorok@gmail.com</a>>:<br><blockquote type="cite">I'm not too keen about seeing buildbots play with trunk ;)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">How about starting simple, and just auto-tagging builds that work?<br></blockquote><blockquote type="cite">Could be done per OS/arch, and one global tag when all buildbots pass.<br></blockquote><br>I don't know anything about svn performance. Would this negatively<br>impact llvm.org, which is already pretty strained?<br><br></div></blockquote><div><br></div><div>How is this any different then the buildbots displaying the revision tag for a build that works? And the definition of "works" I assume you mean build and make check cleanly. llvm-test is a different beast and you need to compare from one run to the next because we do not currently pass for everything (which is the job of the nightly tester in theory).</div><div><br></div><div>Also, llvm.org is severely strained right now. We are upgrading the server but I need a few weeks for this. If its possible, it would be nice to have the buildbots update and not do a full check out.</div><div><br></div><div>-Tanya</div><br><blockquote type="cite"><div>If this is reasonable I think I can update my buildbots to do this<br>fairly easily. The global tag is difficult since it requires<br>coordination, but individual tags would be easy. It would be nice to<br>get the mails from them filtered out, otherwise it will make the<br>commit list very noisy.<br><br><blockquote type="cite">It would also be useful to have a SVN pre/post-commit hook display the<br></blockquote><blockquote type="cite">number of current buildbot failures,<br></blockquote><blockquote type="cite">as a reminder that trunk is broken.<br></blockquote><br>I think this would have a negative performance impact, at least until<br>llvm.org is running the public buildmaster.<br><br> - Daniel<br><br><blockquote type="cite">Best regards,<br></blockquote><blockquote type="cite">--Edwin<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">LLVM Developers mailing list<br></blockquote><blockquote type="cite"><a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a><br></blockquote><blockquote type="cite"><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br></blockquote><blockquote type="cite"><br></blockquote><br>_______________________________________________<br>LLVM Developers mailing list<br><a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br></div></blockquote></div><br></body></html>