similar to: NUT and Buildbot (was Re: New Mustek UPS model working)

Hello, first of all I'd like to thank all the NUT developers for their gorgeous work and for their efforts to make NUT the best and most complete UPS management software I've ever seen (seriously). Secondarily I'd like to help the NUT project as far as my help is needed, I'm not a programmer (by now...) but I would like to help somehow anyway. I have 3 UPS from the same

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

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

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 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

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 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

On 11/18/2013 11:57 AM, Mikael Lyngvig wrote: > I'm in the process of configuring a Mac Mini G4 (PowerPC, big-endian) to be > an LLD buildbot slave, as there were some who wanted a big-endian tester of > LLD. > > I have a few quick questions with respect to that: > > 1. LLD appears to be built using Clang, but Clang is not built as part of > the LLD build. So which

I'm in the process of configuring a Mac Mini G4 (PowerPC, big-endian) to be an LLD buildbot slave, as there were some who wanted a big-endian tester of LLD. I have a few quick questions with respect to that: 1. LLD appears to be built using Clang, but Clang is not built as part of the LLD build. So which version of Clang should I use? v3.3 or any nightly build of Clang. Is it enough that

On Jan 24, 2010, at 10:25 AM, clepple+buildbot at ghz.cc wrote: > The Buildbot has detected a new failure of FreeBSD-i686 on Network > UPS Tools. > Full details are available at: > http://buildbot.ghz.cc/public/nut/builders/FreeBSD-i686/builds/62 > > Buildbot URL: http://buildbot.ghz.cc/public/nut/ > > Buildslave for this Build: nine-forty-four > > Build Reason:

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

On Wed, Dec 3, 2008 at 10:19 PM, <clepple+buildbot at ghz.cc> wrote: > The Buildbot has detected a new failure of FreeBSD-6.2-i686. > Full details are available at: > http://buildbot.ghz.cc/public/nut/FreeBSD-6.2-i686/builds/123 Looks like this was the error: ../../drivers/lakeview_usb.c:58: warning: implicit declaration of function `usb_comm_fail'

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

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:

On Feb 17, 2012, at 5:16 AM, Arnaud Quette wrote: > 2012/2/17 <clepple+buildbot at ghz.cc>: >> The Buildbot has detected a new failure on builder MacOSX-10.6-x86 while building Network UPS Tools. >> Full details are available at: >> http://buildbot.networkupstools.org/public/nut/builders/MacOSX-10.6-x86/builds/9 >> >> Buildbot URL:

How would I go about registering a machine with the LLVM buildbot as a build slave? I now have a fairly stable linux-x86_64 machine to add to the pool. -Dave

Since I've heard about AsciiDoc (thanks ESR), I'm in the process of revamping the full Network UPS Tools documentation and website. Without going into the usual "it curred my desease, got my wife back home, and made me won a billion", it really saved my life ^_ ^ I was searching for such tool for years! thanks a lot Stuart and others. Kudos for the work! NUT revamp is not yet

Hi, Here's my first draft proposal for a document on how to setup a Windows box for building LLVM and Clang using MinGW(32/64). The document can serve equally as a procedure for how to configure a Windows box to build LLVM and Clang using MinGW(32/64), and as a procedure for how to set up a build slave. The only thing that is untested is the actual procedure of registering a buildbot slave

On Wed, Nov 13, 2013 at 4:53 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi guys, > > I have this ODROID XU (quad-core ARMv7 Cortex A15 1,6 GHz) box that I want > to make available to the LLVM project. I can see that LLVM already has an > ARMv7 Cortex A9 system doing Clang, but how should this box be used, if at > all? We're talking a long-term commitment

Hongbin, Did you tweak sys.path? # Extend paths to allow loading zorg and config modules. import os, sys path = os.path.join(os.environ.get('HOME'), 'zorg', 'buildbot', 'osuosl', 'master') if path not in sys.path: sys.path.append(path) path = os.path.join(os.environ.get('HOME'), 'zorg') if path not in sys.path: sys.path.append(path)