Hi, My New Year's resolution is to complain (constructively) whenever I get a spurious build failure email from a buildbot. For new or infrequent contributors especially, they can be extremely confusing and unnecessarily alarming. This one below is the first build ever attempted by the builder, so how on earth can it have come up with a meaningful blame list? And in any case, surely we should only get emailed when something breaks, i.e. on a transition from green to red? In this case there was no previous build whatsoever, let alone a successful one. Thanks, Jay. On 12 January 2015 at 19:54, <llvm.buildmaster at lab.llvm.org> wrote:> The Buildbot has detected a new failure on builder ppc64le-sanitizer while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/ppc64le-sanitizer/builds/0 > > Buildbot URL: http://lab.llvm.org:8011/ > > Buildslave for this Build: ppc64le-sanitizer > > Build Reason: scheduler > Build Source Stamp: [branch trunk] 225670 > Blamelist: ab,abataev,alexfh,artagnon,benlangmuir,chandlerc,chapuni,compnerd,dexonsmith,djasper,dsanders,ehsan,eugenis,foad,gribozavr,hfinkel,jhibbits,jkolek,joerg,majnemer,matze,nathan,rafael,rdivacky,rksimon,rsmith,rtrieu,sanjoy,seurer,spatel,timurrrr,tomatabacu,tstellar > > BUILD FAILED: failed annotate > > sincerely, > -The Buildbot
Timur Iskhodzhanov
2015-Jan-12 21:37 UTC
[LLVMdev] buildbot failure in LLVM on ppc64le-sanitizer
Hi Jay, Please bear in mind that quite a lot of buildbot-related issues you'll see are, well, caused by bugs/features of buildbot source code rather than the configs used for the LLVM master. I'm not familiar with the LLVM master configs per se, but from my experience setting up buildbots for other projects, there are dozens of features in buildbot you'll find weird. And in most cases, those are not actionable for LLVM developers, so not sure I support your resolution :) Flaky tests and/or undecipherable LIT test outputs are good reasons to complain though. In this particular case, it looks like the bot has just been added [and is unlikely to be green for the first few cycles/days], so it seems reasonable to just disable email notifications for it. I don't know who has added the bot, so adding Galina and Kostya to CC, they should know. –– Tim On Tue Jan 13 2015 at 12:07:23 AM Jay Foad <jay.foad at gmail.com> wrote:> Hi, > > My New Year's resolution is to complain (constructively) whenever I > get a spurious build failure email from a buildbot. For new or > infrequent contributors especially, they can be extremely confusing > and unnecessarily alarming. > > This one below is the first build ever attempted by the builder, so > how on earth can it have come up with a meaningful blame list? And in > any case, surely we should only get emailed when something breaks, > i.e. on a transition from green to red? In this case there was no > previous build whatsoever, let alone a successful one. > > Thanks, > Jay. > > On 12 January 2015 at 19:54, <llvm.buildmaster at lab.llvm.org> wrote: > > The Buildbot has detected a new failure on builder ppc64le-sanitizer > while building llvm. > > Full details are available at: > > http://lab.llvm.org:8011/builders/ppc64le-sanitizer/builds/0 > > > > Buildbot URL: http://lab.llvm.org:8011/ > > > > Buildslave for this Build: ppc64le-sanitizer > > > > Build Reason: scheduler > > Build Source Stamp: [branch trunk] 225670 > > Blamelist: ab,abataev,alexfh,artagnon,benlangmuir,chandlerc,chapuni, > compnerd,dexonsmith,djasper,dsanders,ehsan,eugenis,foad, > gribozavr,hfinkel,jhibbits,jkolek,joerg,majnemer,matze, > nathan,rafael,rdivacky,rksimon,rsmith,rtrieu,sanjoy, > seurer,spatel,timurrrr,tomatabacu,tstellar > > > > BUILD FAILED: failed annotate > > > > sincerely, > > -The Buildbot > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150112/859020bd/attachment.html>
Alexey Samsonov
2015-Jan-13 00:20 UTC
[LLVMdev] buildbot failure in LLVM on ppc64le-sanitizer
Hi Jay, This should hopefully be fixed by http://reviews.llvm.org/D6934 (by Will) On Mon, Jan 12, 2015 at 1:37 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote:> Hi Jay, > > Please bear in mind that quite a lot of buildbot-related issues you'll see > are, well, caused by bugs/features of buildbot source code rather than the > configs used for the LLVM master. > > I'm not familiar with the LLVM master configs per se, but from my > experience setting up buildbots for other projects, there are dozens of > features in buildbot you'll find weird. And in most cases, those are not > actionable for LLVM developers, so not sure I support your resolution :) > > Flaky tests and/or undecipherable LIT test outputs are good reasons to > complain though. > > In this particular case, it looks like the bot has just been added [and is > unlikely to be green for the first few cycles/days], so it seems reasonable > to just disable email notifications for it. > I don't know who has added the bot, so adding Galina and Kostya to CC, > they should know. > > –– > Tim > > On Tue Jan 13 2015 at 12:07:23 AM Jay Foad <jay.foad at gmail.com> wrote: > >> Hi, >> >> My New Year's resolution is to complain (constructively) whenever I >> get a spurious build failure email from a buildbot. For new or >> infrequent contributors especially, they can be extremely confusing >> and unnecessarily alarming. >> >> This one below is the first build ever attempted by the builder, so >> how on earth can it have come up with a meaningful blame list? And in >> any case, surely we should only get emailed when something breaks, >> i.e. on a transition from green to red? In this case there was no >> previous build whatsoever, let alone a successful one. >> >> Thanks, >> Jay. >> >> On 12 January 2015 at 19:54, <llvm.buildmaster at lab.llvm.org> wrote: >> > The Buildbot has detected a new failure on builder ppc64le-sanitizer >> while building llvm. >> > Full details are available at: >> > http://lab.llvm.org:8011/builders/ppc64le-sanitizer/builds/0 >> > >> > Buildbot URL: http://lab.llvm.org:8011/ >> > >> > Buildslave for this Build: ppc64le-sanitizer >> > >> > Build Reason: scheduler >> > Build Source Stamp: [branch trunk] 225670 >> > Blamelist: ab,abataev,alexfh,artagnon,benlangmuir,chandlerc,chapuni, >> compnerd,dexonsmith,djasper,dsanders,ehsan,eugenis,foad, >> gribozavr,hfinkel,jhibbits,jkolek,joerg,majnemer,matze, >> nathan,rafael,rdivacky,rksimon,rsmith,rtrieu,sanjoy, >> seurer,spatel,timurrrr,tomatabacu,tstellar >> > >> > BUILD FAILED: failed annotate >> > >> > sincerely, >> > -The Buildbot >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-- Alexey Samsonov vonosmas at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150112/1fd3c118/attachment.html>
Possibly Parallel Threads
- [LLVMdev] buildbot failure in LLVM on clang-amd64-openbsd
- Fwd: buildbot failure in LLVM on clang-ppc64-elf-linux2
- [LLVMdev] buildbot failure in LLVM on clang-native-mingw64-win7
- Fwd: buildbot failure in LLVM on clang-ppc64-elf-linux2
- [LLVMdev] cross-section differences in MC generation