similar to: [nut-commits] buildbot failure in Network UPS Tools on Fedora-x64

This has been fixed in trunk but not yet merged in EatonSDK branch; Fred On Wed, 2012-02-08 at 19:44 -0500, clepple+buildbot at ghz.cc wrote: > The Buildbot has detected a new failure on builder AIX-powerpc while building Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/AIX-powerpc/builds/20 > > Buildbot URL:

Why does GN bot still send mails? I thought it got fixed? On Wed, Jul 3, 2019 at 1:44 PM <llvm.buildmaster at lab.llvm.org> wrote: > > The Buildbot has detected a new failure on builder sanitizer-x86_64-linux-gn while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-gn/builds/1820 > > Buildbot URL:

Why is there a public GN buildbot that sends emails and IRC notifications? That isn't what was agreed upon. Either un-GM it, or silence it. Roman. On Fri, Jun 28, 2019 at 1:05 AM <llvm.buildmaster at lab.llvm.org> wrote: > > The Buildbot has detected a new failure on builder sanitizer-x86_64-linux-gn while building llvm. > Full details are available at: >

These URLs don't work for me. How do I know what is broken? It builds fine on my x86 linux box. -----Original Message----- From: buildbot at google1.osuosl.org [mailto:buildbot at google1.osuosl.org] Sent: Friday, August 07, 2009 5:12 PM To: Sanjiv Kumar Gupta - I00171 Cc: llvm-testresults at cs.uiuc.edu Subject: buildbot failure in llvm on llvm-i686-linux The Buildbot has detected a new

Chetan, the below error is the same than on Solaris Intel: buildbot startup script needs to have PATH set so that it can find the various needed binaries (svn, make, compiler, ...) you may simply want to copy the intel one to the sparc... I'm away from work and back on Jan. 3rd, so up to you to fix it. cheers, Arnaud 2011/12/21 <clepple+buildbot at ghz.cc> > The Buildbot has

Hey Alexey, This bot has been failing for a week, by the looks of it - what's the deal? On Thu, May 7, 2015 at 7:31 PM, <llvm.buildmaster at lab.llvm.org> wrote: > The Buildbot has detected a new failure on builder sanitizer-x86_64-linux > while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/17810 >

I’ve had another look, and some of the failing tests don’t use temporary files, so I don’t think this is a case of tests having side-effects. Instead, I’ve noticed that in the build log (http://lab.llvm.org:8011/builders/llvm-clang-x86_64-expensive-checks-win/builds/6552/steps/build-unified-tree/logs/stdio), llvm-tblgen.exe is built (my patch modified it), but the table-generation steps of the

On Fri, Aug 7, 2009 at 9:18 AM, <Sanjiv.Gupta at microchip.com> wrote: > These URLs don't work for me. How do I know what is broken? > It builds fine on my x86 linux box. Why don't the URLs work for you? In this case the problem was just because llvm.org went down. When an "svn" step fails; i.e., the line after "BUILD FAILED:", the problem is usually

This buildbot has been failing for over a week straight ( http://lab.llvm.org:8011/builders/clang-cmake-mips/builds/9387 ) - does anyone know/care about it? ---------- Forwarded message ---------- From: <llvm.buildmaster at lab.llvm.org> Date: Wed, Sep 30, 2015 at 7:49 PM Subject: buildbot failure in LLVM on clang-cmake-mips To: Adrian Prantl <aprantl at apple.com>, Ahmed Bougacha

This bot seems kind of flaky. In the last 100 builds, it has failed "gdb-75-check" 22 times with what is either a linker error or a missing header (or both?): gdb compile failed, /usr/bin/ld: error: /home/buildslave/osuosl_slave/clang-x86_64-ubuntu-gdb-75/clang-tests/build/gdb/testsuite/gdb.trace/pendshr1.c.o: requires dynamic R_X86_64_PC32 reloc against 'pendfunc1' which

Should "lit :: shtest-format.py" (from check-lit) be marked unsupported on PS4? It seems flakey there. This evening, it failed on my commit, r337514, and I'm fairly confident it wasn't my commit's fault. Then it recovered on the next commit. http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast/builds/33502

I'm sure it's obvious and I'm just blind, but I can't find the relevant part of that build that's showing a crash. Can you help me out? On Fri, May 8, 2015 at 1:49 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: > +Sergey > > The bot failed on (and looks like it still fails even after LLVM r236877) > on AddressSanitizer-i386-linux ::

Just received this: The Buildbot has detected a new failure of llvm-ppc-linux on llvm. Full details are available at: http://google1.osuosl.org:8011/builders/llvm-ppc-linux/builds/3229 Buildbot URL: http://google1.osuosl.org:8011/ Buildslave for this Build: nick1 Build Reason: Build Source Stamp: 84759 Blamelist: ofv BUILD FAILED: failed compile Apparently the problem was a warning at

On Mon, Jan 14, 2013 at 4:36 AM, Arnaud Quette <aquette.dev at gmail.com> wrote: > Hey Charles, > > I hope you're doing fine... > > There seems to be an issue on your BSD: permission denied on Asciidoc > generation. It looks like this is due to a new version of AsciiDoc (8.6.8 vs 8.6.6). I'll take a look again later, but I doubt it's related to the most recent

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

Alexey, I got mail from one of the tsan buildbots, claiming a breakage in tsan tests. But I cannot see anything on the logs it has for the build. http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/17916/steps/run%2064-bit%20tsan%20unit%20tests/logs/stdio Any ideas? Thanks. Diego. ---------- Forwarded message ---------- From: <llvm.buildmaster at lab.llvm.org> Date: Wed,

On Aug 7, 2009, at 10:13 AM, Daniel Dunbar wrote: > On Fri, Aug 7, 2009 at 9:18 AM, <Sanjiv.Gupta at microchip.com> wrote: >> These URLs don't work for me. How do I know what is broken? >> It builds fine on my x86 linux box. > > Why don't the URLs work for you? > I suspect the corporate firewall is blocking outgoing connections on port 8011. -jim > In

This buildbot seems to have been failing continuously for a couple of weeks now ( http://lab.llvm.org:8011/builders/llvm-mips-linux/builds/14658 ) - is anyone watching it/caring about it? ---------- Forwarded message ---------- From: <llvm.buildmaster at lab.llvm.org> Date: Wed, Sep 30, 2015 at 11:34 PM Subject: buildbot failure in LLVM on llvm-mips-linux To: Ahmed Bougacha

On Thu, Oct 1, 2015 at 12:08 PM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > I do. I'll take a look. > > Is there a way for owners to get emails for long-lasting failures? > I'm not sure what the generic setup is, but at least for the builder/slave I admin, it emails me on every failure. So I get a lot of mail, continuously, if there's a consistent

vitalybuka, sanitizer-x86_64-linux-gn is _still_ on http://lab.llvm.org:8011/console . Can we please get it removed? On Wed, Jul 3, 2019 at 7:07 AM Nico Weber <thakis at chromium.org> wrote: > https://reviews.llvm.org/D63909 landed. Maybe it needs a master restart > to have an effect? > > On Wed, Jul 3, 2019 at 1:03 PM Roman Lebedev <lebedev.ri at gmail.com> wrote: >