search for: buildbotted

Hi, I had cloned zorg from https://llvm.org/svn/llvm-project/zorg/trunk, then I try to start the buildbot master located in buildbot/osuosl/master (the absolute path is /nfs/home/hongbin.zheng/buildbot/zorg/buildbot/osuosl/master) by simply typing "buildbot start" And I get something like this from my twistd.log: --- <exception caught here> --- File

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)

Hi All, Recent conversations [1][2] would suggest we need to rethink zorg or at the very least improve the documentation. I've CC'ed Daniel Dunbar, Galina Kistanova and Duncan Sands because it seemed that they have contributed the most code to Zorg Organisation ========= The current organisation of the Zorg repository doesn't make a huge amount of sense from my perspective. There

> The Buildbot has detected a new failure of Ubuntu-lucid-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-lucid-x86/builds/78 If I understand this correctly, there are multiple copies of some of the man page names in the automake variables: /usr/bin/install -c -m 644 ../../../docs/man/nut.conf.5

Hi folks, *tl;dr* I'm having some trouble setting up a Windows buildbot and I'm looking for someone with LLVM-on-Windows experience to help me. *Long story* Hans Wennborg recently pointed <http://lists.llvm.org/pipermail/llvm-dev/2020-May/141803.html>out <http://lists.llvm.org/pipermail/llvm-dev/2020-May/141803.html>, that we're missing a 32 bit Windows buildbot and I

On Tue, Mar 22, 2016 at 5:03 PM, David Blaikie <dblaikie at gmail.com> wrote: > Could we change the buildbot config to treat > warnings-as-errors-that-continue in the build step? (so we get the benefit > of further execution tests, while still sending fail-mail, etc for the > warning?) > > That sounds reasonable, although the buildbot implementation seems to be pretty

On 2009-07-15 23:24, Dale Johannesen wrote: > On Jul 15, 2009, at 11:52 AMPDT, Stuart Hastings wrote: > > >> We've had a lot of churn in all the trunks (llvm, llvm-gcc, clang) >> recently, and the testing buildbots have been failing repeatedly. >> >> I spoke with Chris this AM, and he suggested we have a "stabilization >> day." Please avoid

Greetings, I would like to propose adding a buildbot which builds with -Werror. The reason for a new buildbot in this configuration is twofold: 1. It helps users who track and release from ToT, because they (generally) seem to build with -Werror. Speaking from experience :-), new warnings tend to crop up in a large range of commits, and end up blocking one or more of these downstream users.

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

Hi all, There's been a recent bootstrap failure that might be covered up because of another failure. I just wanted to point this out so that people can take a look: -bw Here's the failure from our buildbot: Assertion failed: (DestReg == VirtReg && "Unknown load situation!"), function RewriteMBB, file /Volumes/Sandbox/Buildbot/llvm/build.llvm-

> > Ah! This is the one that's messing up. Could someone take a look at > this and see why it's failing? It doesn't even seem to be getting to > the "svn" checkout. > > Hi Bill, [sorry I was not subscribed to llvm-testresults, and noticed this only now] This is a buildbot bug apparently, see http://buildbot.net/trac/ticket/284 and

That would explain it. The commit messages were quite long (especially the second one) and a commit with a smaller message has shown up. Thanks for letting me know. I'll try to keep them a bit more reasonable in future. > -----Original Message----- > From: NAKAMURA Takumi [mailto:geek4civic at gmail.com] > Sent: 15 November 2013 16:28 > To: Daniel Sanders > Cc: LLVM Developers

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

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

Could we change the buildbot config to treat warnings-as-errors-that-continue in the build step? (so we get the benefit of further execution tests, while still sending fail-mail, etc for the warning?) On Tue, Mar 22, 2016 at 5:00 PM, David Jones via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Greetings, > > I would like to propose adding a buildbot which builds with -Werror. The

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 Thu, Jul 16, 2009 at 7:42 AM, David Greene<dag at cray.com> wrote: > On Wednesday 15 July 2009 15:43, Török Edwin wrote: > >> How about starting simple, and just auto-tagging builds that work? >> Could be done per OS/arch, and one global tag when all buildbots pass. > > We've talked about this before and I've been working on setting up > such a system.

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 2014 Dec 10, at 08:40, Tom Stellard <tom at stellard.net> wrote: > > On Tue, Dec 09, 2014 at 09:22:16PM -0800, Duncan P. N. Exon Smith wrote: >> The `Metadata`/`Value` split (PR21532) landed in r223802 -- at least, the >> C++ side of it. This was a rocky day, but I suppose that's what I get >> for failing to stage the change in smaller pieces. >>

Ah, ...no. please don't hesitate to write logs ;) It must be the subject in the buildbot, not in developer guys. Galina, I'll write up later, how to tweak this issue. It is not resolved in released versions, though. The easiest way is to tweak svnpoller. 2013/11/16 Daniel Sanders <Daniel.Sanders at imgtec.com>: > That would explain it. The commit messages were quite long