<div dir="ltr"><div class="gmail_quote">On Wed, 20 May 2015 at 02:55 Chris Matthews <<a href="mailto:chris.matthews@apple.com">chris.matthews@apple.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Just some stats, after looking through <a href="http://lab.llvm.org" target="_blank">lab.llvm.org</a>:8011<div><br></div><div>Maybe these should be marked as experimental, and removed from the builders link on the main page.</div><div><br></div><div><div>Never passed at all:</div><div>libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03</div><div>libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan</div><div>libcxx-libcxxabi-x86_64-linux-ubuntu-tsan</div><div>libcxx-libcxxabi-x86_64-linux-ubuntu-gcc</div><div>libcxx-libcxxabi-x86_64-apple-darwin14-system-lib</div><div>lldb-x86_64-ubuntu-14.04-android</div><div>llgo-x86_64-linux</div></div></div></blockquote><div><br></div><div>Hi,</div><div><br></div><div>llgo-x86_64-linux is mine. Sorry, I had disabled the slave agent to avoid spurious emails, but hadn't considered its impact on the status pages. I'm fine with disabling it altogether for now; I'm waiting on a fix to Ninja to be merged.<br></div><div><br></div><div>Cheers,</div><div>Andrew</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div>Not pass in at least a month:</div><div><br></div><div>llvm-clang-lld-x86_64-debian-fast</div><div>clang-native-mingw32-win7</div><div>clang-x86_64-linux-selfhost-abi-test</div><div>clang-x64-ninja-win7-debug</div><div>perf-x86_64-penryn-O3-polly-detect-only</div><div>sanitizer-x86_64-linux-bootstrap</div><div>sanitizer_x86_64-freebsd</div><div>sanitizer-windows</div><div>libcxx-libcxxabi-x86_64-apple-darwin14-tot-clang</div><div>clang-amd64-openbsd</div><div>lldb-x86_64-debian-clang</div><div>lldb-x86_64-freebsd</div><div>lldb-x86_64-ubuntu-14.10</div></div></div><div style="word-wrap:break-word"><div><br></div><div><br><div><blockquote type="cite"><div>On May 19, 2015, at 11:32 AM, David Blaikie <<a href="mailto:dblaikie@gmail.com" target="_blank">dblaikie@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 19, 2015 at 10:40 AM, James Y Knight <span dir="ltr"><<a href="mailto:jyknight@google.com" target="_blank">jyknight@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yes, I also find the amount of bot spam in #llvm is basically intolerable. It makes it difficult to see actual people talking. At first, I just put all the bots on /ignore. Now I have an xchat script to move the botspam to another tab (<a href="http://tabify-004.pl/" target="_blank">tabify-004.pl</a>). I'd recommend that the bots should just be moved to #llvm-bots and fix the problem for everyone. Those who are committing changes can join that channel, too, and others don't care.<div><div><br></div><div>While we're on this subject, I also find the official buildbot page (<a href="http://lab.llvm.org:8011/" target="_blank">lab.llvm.org:8011</a>) almost unusable, since so many columns are either always red, or else are so flaky that they basically randomly alternate between passing and failing. So, at a glance, it's impossible to tell whether the current state of the tree is good. (I certainly haven't memorized which ones are "supposed" to be red, and which are not. Maybe others have). Having flaky and always-failing builds show up on the buildbot pages, and notifying IRC, really has negative utility, since it not only is not providing useful information, but is serving to obscure the actual important failures, and causing people to spend time investigating non-problems.</div><div><br></div><div>Someone gave me the hint to use the <a href="http://bb.pgr.jp/" target="_blank">http://bb.pgr.jp/</a> buildbot page instead, which was a great recommendation -- that page shows problems much more clearly. But it's unfortunate that there *needs* to be a separate "sane builders only" buildmaster.</div><div><br></div><div>E.g. (and not to pick on this particular bot, this is just one example of many): <a href="http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/27655" target="_blank">http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/27655</a> -- passed, while the previous failed. But, it's not caused by the commit, it's just arbitrary.</div><div><br></div><div>Or, yesterday, on #llvm: "Anyone want to give me a clue as to why this bot failed? <a href="http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/18017" target="_blank">http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/18017</a>" -- answer: because it's randomly broken. Wasted the questioner's time trying to investigate the failure.<br></div></div></div></blockquote><div><br>Whenever you get crappy fail-mail, please forward it to llvm-dev, cc'ing the bot owner and request the issue be addressed or the bot be removed. Yeah, I know it's not an ideal process, but it's something to keep issues visible/pushed on.<br><br>But, yes, having some more formal process to deal with this sort of thing would be nice (I can imagine some process along the lines of "bots start in experimental and need a track record of low flake/false positive results for some period of time before being promoted out of experimental so they can send mail to blame lists and IRC, etc" coupled with some mechanism for demoting a buildbot back into experimental if it starts behaving poorly)<br><br>- David<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div></div><div><br></div></div><div><br></div><div><span style="font-size:12.8000001907349px">If all the flaky or always-broken builder configurations got hidden from the main pages of buildbot, and stopped sending emails/IRC notifications to anyone but their "owner", that would be a substantial improvement.</span><div style="font-size:12.8000001907349px"></div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><span>On Tue, May 19, 2015 at 10:15 AM, Renato Golin <span dir="ltr"><<a href="mailto:renato.golin@linaro.org" target="_blank">renato.golin@linaro.org</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>Folks,<br>
<br>
I know it's a reasonably valuable thing to have the buildbot IRC bot<br>
publishing results, but the channel is kind of flooded with the<br>
messages, and the more bots we put up, the worse it will be.<br>
<br>
I think we still need the NOC warnings, but not over IRC. The Buildbot<br>
NOC page is horrible and useless, since it doesn't know the difference<br>
between "it's red and I know it" from "it's broken".<br>
<br>
For that reason, I have built my own NOC page:<br>
<br>
<a href="http://people.linaro.org/~renato.golin/llvm/arm-bots/" target="_blank">http://people.linaro.org/~renato.golin/llvm/arm-bots/</a><br>
<br>
But that machine is too slow to cope with all bots. We may need a<br>
project to build such a system on a larger scale.<br>
<br>
However, for now, I think not printing the green results in IRC would<br>
go a long way of cleaning the channel up.<br>
<br>
Any thoughts?<br>
<br>
cheers,<br>
--renato<br>
_______________________________________________<br></span><span>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
</span></blockquote></div><br></div>
<br>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu/" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
<br></blockquote></div><br></div></div>
_______________________________________________<br>cfe-dev mailing list<br><a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br></div></blockquote></div><br></div></div>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
</blockquote></div></div>