<div dir="ltr">Starting a separate thread on this that's easier to find :-)<div><br></div><div>I see these two buildbots for lldb:</div><div><br></div><div><div>lldb-x86_64-darwin12</div><div>lldb-x86_64-debian-clang<br>
</div><div><br></div><div><div>The first one looks like a MacOSX buildbot that runs an Xcode lldb-tool build (basically what I do) and is failing in the llvm/clang build phase without a whole lot of detail as to why. It's been not building for some time. I assume Apple owns this one?</div>
<div><br></div><div><br></div><div>lldb-x86_64-debian-clang<br></div><div><br></div><div>This one appears to have some tests that fail that make it show purple. Not sure exactly what the configuration is here.</div><div>
<br></div><div><br></div><div>From recent activity, it seems like we could use a few more:</div><div><br></div><div><ul><li>lldb ubuntu 14.04 x86_64 (clang-built)</li><li>lldb Windows (something - VS 2013? Windows 8.1 or 7?)</li>
<li>FreeBSD (10 only? 9? x86_64 only?)</li></ul><div>One thing I'd love to see is a way to force me to know that (at the very least) the build itself (i.e. compile/link/packaging) failed in way that I cannot escape. i.e. send nag mail to the mailing list.<br>
</div></div><div><br></div><div>However, I also don't want to hear noise in the lldb-dev list (or an lldb-build list or something) every time a flaky test intermittently fails. So for me, I'd prefer to just be forced to know about build failures but I'd prefer to see test failures on a build grid UI and not be nagged on every false alarm. Without the build break email alarm, I'm not sure how we best would get people to know the build is broken somewhere. Thoughts?</div>
<div><br></div><div>I had intended to take ownership of pushing this one forward:</div><div><ul><li>lldb ubuntu 14.04 x86_64 (clang-built)</li></ul><div>No promises on timing, but now that I got the initial llgs in, this is a fine time to start addressing this.</div>
</div><div><br></div>-- <br><div dir="ltr"><table cellspacing="0" cellpadding="0" style="color:rgb(136,136,136);font-family:'Times New Roman'"><tbody><tr style="color:rgb(85,85,85);font-family:sans-serif;font-size:small">
<td nowrap style="border-top-style:solid;border-top-color:rgb(213,15,37);border-top-width:2px">Todd Fiala |</td><td nowrap style="border-top-style:solid;border-top-color:rgb(51,105,232);border-top-width:2px"> Software Engineer |</td>
<td nowrap style="border-top-style:solid;border-top-color:rgb(0,153,57);border-top-width:2px"> <a href="mailto:tfiala@google.com" style="color:rgb(17,85,204)" target="_blank"><span style="color:rgb(34,34,34);background-color:rgb(255,255,204)">tfiala@google.com</span></a> |</td>
<td nowrap style="border-top-style:solid;border-top-color:rgb(238,178,17);border-top-width:2px"><font color="#1155cc"> <a>650-943-3180</a></font></td></tr></tbody></table><br></div>
</div></div></div>