similar to: Upgraded Buildbot

On Jan 15, 2014, at 10:18 AM, Emilien KIA wrote: > 2014/1/15 Charles Lepple <clepple at gmail.com>: >> Emilien, >> >> just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! >> We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. > > I am just fixing some bugs

2014/1/15 Charles Lepple <clepple at gmail.com>: > Emilien, > > just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! > We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. I am just fixing some bugs and implementing some minor windows-specific features. > The problem is that

Emilien, just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. The problem is that we do not have a good branch in Git to work from. The windows_port branch got rebased, but since it has merge commits, it is a bit of a mess. I apologize for

Hi Paula, This error is fine. The buildbot has tested the worker version. 0.8.x apparently does not have that method. The error gets handled gracefully on the server side. At least it seems so so far. That should not prevent your bot from connecting. Thanks Galina On Thu, Oct 8, 2020 at 2:11 PM Paula Askar <paulatoth at google.com> wrote: > Hey Andrzej, > > What are you seeing

On Mon, Nov 12, 2012 at 7:03 AM, David Tweed <david.tweed at arm.com> wrote: >> I don't believe so - I think only a certain sliding window of logs are >> kept (& I don't know of an easy way to view a particular revision >> across the bots either) > > For me a bigger issue has been inability to see a long list of results for a > particular builder (say,

The host c++ standard library is missing <utility>, it appears. On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > Please use the correct link : > http://63.145.236.72:8011 > and ignore the previous. > > Also log for broken build is here: > > make[1]: Entering directory >

Please use the correct link : http://63.145.236.72:8011 and ignore the previous. Also log for broken build is here: make[1]: Entering directory `/home/buildslave/zorg/buildbot/osuosl/slave/clang-native-arm-cortex-a9/llvm/lib/Support' llvm[1]: Compiling APFloat.cpp for Release+Asserts build llvm[1]: Compiling APInt.cpp for Release+Asserts build In file included from APFloat.cpp:15: In file

On 14 November 2013 17:43, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Renato, thanks for your elaborate walk-through of the issues with ARM > boards. I'm trying to add some of this to the "How to Build on ARM" > document and will submit a patch later on. > Nice, thanks! That would be great! Unfortunately, my personal budget does not allow me more than a

All, If you are looking for the old "waterfall" view, it has moved to here: http://buildbot.ghz.cc/public/nut/waterfall You might have to shift-reload the page to get the new CSS files. There are a bunch of useful views listed here: http://buildbot.ghz.cc/public/nut/ Let me know if you see any room for improvement. - Charles

On Tue, Sep 29, 2015 at 10:38 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 29 September 2015 at 18:22, David Blaikie <dblaikie at gmail.com> wrote: > > This buildbot looks like it's been failing since Friday - does anyone > > know/own/care about it? > > Yes, we're looking into it. > > As you probably noticed, debugging ARM buildbots are

Yeah. That code has been there since r91421 and wouldn't have failed recently otherwise. Did something change on the host? -eric On Sep 20, 2011, at 11:27 AM, Jim Grosbach wrote: > The host c++ standard library is missing <utility>, it appears. > > > On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > >> Please use the correct link : >>

Switched all but PPC, I don't have access to them. But they run the same script as sanitizer-x86_64-linux. http://lab.llvm.org:8014/#/waterfall?tags=sanitizer On Mon, 12 Oct 2020 at 19:19, Galina Kistanova <gkistanova at gmail.com> wrote: > We have a better version of AnnotatedCommand on the staging. It should be > a functional equivalent of the old one. > We need to stress

Hello everybody, I want to put some kind of instruction on how to add new slave to llvm master. I think it should be somewhere on llvm.org, but not sure on exact place. Any comments/suggestions will be appreciated. Thanks Galina If you want to add your build configuration to the LLVM buildbot infrastructure. 1. Check the existing build configurations to make sure the one you are

Our Flang-aarch64 buildbots just won't connect to the main Buildbot master anymore. I switched them to the staging buildbot master instead and it seems fine for now. Is there anything that we can/should tweak at our end? http://lab.llvm.org:8014/#/waterfall?tags=flang -Andrzej On 08/10/2020 00:31, Galina Kistanova via cfe-dev wrote: > They are online now -

This buildbot looks like it's been failing since Friday - does anyone know/own/care about it? ---------- Forwarded message ---------- From: <llvm.buildmaster at lab.llvm.org> Date: Mon, Sep 28, 2015 at 7:29 PM Subject: buildbot failure in LLVM on clang-cmake-thumbv7-a15-full-sh To: Adrian Prantl <aprantl at apple.com>, Cameron Esfahani <dirty at apple.com>, Chris Bieneman

I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall It builds every single revision of llvm, runs the testsuite, and reports the results. It takes about 3 minutes per build+test right now (it's an 8 core machine). Currently i have it building x86_64-linux. Setting up a builder/slave for any platform would be trivial. I simply don't have machines running anything but

On Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via lldb-commits < lldb-commits at lists.llvm.org> wrote: > They are online now - http://lab.llvm.org:8011/#/waterfall?tags=sanitizer > > AnnotatedCommand has severe design conflict with the new buildbot. > We have changed it to be safe and still do something useful, but it will > need more love and care. > > Please let me

On Monday 10 November 2008 15:28, Bill Wendling wrote: > Hi Daniel, > > I see that you're doing a Debug build. Could you do a "Release" or > "Release-Asserts" build instead? This will catch errors which > developers won't normally see. I never knew about buildbot until just now. This could really help with the validation proposal I just posted. Can

Hi Daniel, I see that you're doing a Debug build. Could you do a "Release" or "Release-Asserts" build instead? This will catch errors which developers won't normally see. -bw On Sun, Nov 2, 2008 at 1:02 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall > It builds every single

Daniel, Thanks! Is this doing a build of Ada and Fortran? :-) -bw On Sun, Nov 2, 2008 at 1:02 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall > It builds every single revision of llvm, runs the testsuite, and > reports the results. It takes about 3 minutes per build+test right > now (it's an 8