similar to: Buildbot master upgrade

The Buildbot master software has finally been upgraded to 0.8.5 here: http://buildbot.networkupstools.org/public/nut/waterfall For those of you with Buildbot slave systems, the /private/nut/ URL is no longer necessary - the same username and password will work in the forms on the new pages (for actions like forcing builds, stopping builds, etc.) Hopefully I will soon be able to fix

On Sep 24, 2011, at 3:54 PM, clepple+buildbot at ghz.cc wrote: > The Buildbot has detected a new failure of FreeBSD-x86 on Network > UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/FreeBSD-x86/builds/266 http://buildbot.ghz.cc/public/nut/builders/FreeBSD-x86/builds/266/steps/compile/logs/stdio : libtool: compile: gcc

On Oct 12, 2011, at 4:11 AM, clepple+buildbot at ghz.cc wrote: > The Buildbot has detected a new failure of Solaris-intel on Network > UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Solaris-intel/builds/133 I should mention that this latest round of buildbot failure emails is misleading - the SVNPoller process wedged itself

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,

I guess I have absorbed a bit of the agile development philosophy, or maybe I am a sucker for automatically generated status displays, but whatever the reason, we now have a Buildbot running: http://buildbot.ghz.cc/public/nut/ The idea is that anytime someone checks a new SVN revision into NUT, the buildbot master will ask the slaves to check out the changes and build NUT. Since the build

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

On Wed, Feb 11, 2009 at 11:30 AM, Fr3ddie <fr3ddie at fr3ddie.it> wrote: > Charles Lepple wrote: >> When something gets updated, you would then run 'svn update' to pull >> the latest changes in. > > Ok. > >> The dependencies are set up such that if only one driver is changed >> during the SVN update, running 'make' on that directory should

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

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 -

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

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

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

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

Citeren clepple+buildbot op ghz.cc: > The Buildbot has detected a new failure of FreeBSD-i686. > Full details are available at: > http://buildbot.ghz.cc/public/nut/FreeBSD-i686/builds/35 Charles, It seems that m4/nut_check_libhal.m4 fails to detect the proper path where to install the .fdi files. I have no idea where these files live on FreeBSD, so could you please find out what

On Jul 29, 2013, at 7:56 AM, Charles Lepple wrote: > On Jul 29, 2013, at 6:43 AM, Pavel Potcheptsov (EKTOS) wrote: > >> Hello list, >> I have explored https://github.com/networkupstools/nut repository >> and found that Riello UPS added into list of supported UPS. >> But current package for most distribution it's nut-2.6.5 which >> doesn't have

I'm looking for a little bit of help with the man page conversion. So far, about a third of the man pages are converted, and I think it would make sense to have a second or third set of eyes compare the output to be sure that we are not losing any information in the conversion process. In the tarballs generated from the AsciiDoc branch on http://buildbot.ghz.cc/public/nut/ you will find the

Hey Charles, 2011/11/24 <clepple+buildbot at ghz.cc>: > The Buildbot has detected a new failure on builder Fedora-x64 while building Network UPS Tools. > Full details are available at: > ?http://buildbot.networkupstools.org/public/nut/builders/Fedora-x64/builds/453 > > Buildbot URL: http://buildbot.networkupstools.org/public/nut/ > > Buildslave for this Build:

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

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

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