<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 05/19/2015 10:40 AM, James Y Knight
wrote:<br>
</div>
<blockquote
cite="mid:CAA2zVHrQy2w6EJrBv+dS6RSv4dys=TgMV=kGmeCmBVXGyJMj=A@mail.gmail.com"
type="cite">
<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 moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__tabify-2D004.pl_&d=AwMD-g&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=ZQEGPuQ3IdYBkUaIH3S_VtXLi0OeD9CtsDVQi1k99ZY&s=BdLwInFVgX2g47QQQc8qTjCfk9hy2VRk9w8I8XSYKN4&e=" 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 moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lab.llvm.org-3A8011_&d=AwMD-g&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=ZQEGPuQ3IdYBkUaIH3S_VtXLi0OeD9CtsDVQi1k99ZY&s=XtRpo9t84lAUAWAxnvam2OHeb8EbCmmnymOg5-gahUE&e=" 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 moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__bb.pgr.jp_&d=AwMD-g&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=ZQEGPuQ3IdYBkUaIH3S_VtXLi0OeD9CtsDVQi1k99ZY&s=4GqCf0KFdWE1cXbM2txCy7p5NAzOxbmyA1gmSdu7nmw&e=" 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 moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lab.llvm.org-3A8011_builders_clang-2Dnative-2Darm-2Dcortex-2Da9_builds_27655&d=AwMD-g&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=ZQEGPuQ3IdYBkUaIH3S_VtXLi0OeD9CtsDVQi1k99ZY&s=4-ZtOmv-fdwIW3ViXXkyX_pHY29DHwwxHT7rKfq4sTI&e=" 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 moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lab.llvm.org-3A8011_builders_sanitizer-2Dx86-5F64-2Dlinux_builds_18017&d=AwMD-g&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=ZQEGPuQ3IdYBkUaIH3S_VtXLi0OeD9CtsDVQi1k99ZY&s=Tibg0fo5Pnx2f7WUO3aU8hOoVrqQa_lTZ_oWc5pf5WI&e=" 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><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>
</div>
</blockquote>
+1, this is a really good summary of issues. I'm in full support of
any and all efforts to reduce noise here. <br>
<br>
I've gotten to the point where I only watch a small handful bots.
Anything other than that, I pretty much ignore unless someone emails
me directly or replies to a commit. I'm not quite to point of
marking buildbot emails as spam, but I'm definitely not paying them
much attention either. One particular irritant is getting emails
12-24 hours later about someone else's breakage that has *already
been fixed*. The long cycling bots are really irritating in that
respect. <br>
<br>
<blockquote
cite="mid:CAA2zVHrQy2w6EJrBv+dS6RSv4dys=TgMV=kGmeCmBVXGyJMj=A@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 19, 2015 at 10:15 AM,
Renato Golin <span dir="ltr"><<a moz-do-not-send="true" href="mailto:renato.golin@linaro.org" target="_blank">renato.golin@linaro.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">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 moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=http-3A__people.linaro.org_-257Erenato.golin_llvm_arm-2Dbots_&d=AwMD-g&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=ZQEGPuQ3IdYBkUaIH3S_VtXLi0OeD9CtsDVQi1k99ZY&s=HHVx2Xqbhd4Hb8BHdV1RaeFV1E6xsJz3Uiwshihemc0&e=" 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>
cfe-dev mailing list<br>
<a moz-do-not-send="true" href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br>
<a moz-do-not-send="true" href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cfe-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>
<a class="moz-txt-link-freetext" href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>