similar to: [LLVMdev] BuildBot Upgrade

On Tuesday 21 July 2009 12:01, Daniel Dunbar wrote: > 6. Configure style builders now use --without-llvmgcc and > --without-llvmgxx to avoid problems with failing Frontend tests. In > the longer term we should add builders which build llvmgcc and do not > have this problem. I have a builder that does this today. When are you checking your stuff into the LLVM repository? I'd

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

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

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 2011-04-08 08:58, Duncan Sands wrote: > Hi Renato, > >> I was recently investigating the build bot infrastructure and noticed >> that the arm-linux target is failing for quite a long time. I believe >> that it means ARM code is not executed all that often in LLVM tests, >> is that correct? Hi i will summarise the last sucessfull builds by the ARM builder:

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

I don't know what failed on llvm-ppc-linux. The build works on my i386-linux. I can't access the said URL. It says "connection refused". - Sanjiv -------- Original Message -------- Subject: buildbot failure in llvm on llvm-ppc-linux Date: Tue, 16 Jun 2009 09:20:25 -0700 From: buildbot at google1.osuosl.org To: Sanjiv Gupta <sanjiv.gupta at microchip.com> CC:

Óscar Fuentes wrote: > 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 >

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 Tobias, > I committed an extended version of that patch to llvm core and the test suite. > Can you have a look, if it works for you. if I configure like this then the configure script thinks llvm-gcc is not dragonegg: configure --with-llvmgcc="gcc-4.5 -fplugin=path/dragonegg.so" --with-llvmgxx="g++-4.5 -fplugin=path/dragonegg.so" There are several reasons for

Hello everyone, Please note that we have 2 new clang cross builders now on http://google1.osuosl.org:8011/waterfall They build the next configurations: --build=x86_64-apple-darwin10 --host=i686-pc-mingw32 --target=i686-pc-mingw32 --build=x86_64-apple-darwin10 --host=x86_64-apple-darwin10 --target=i686-pc-mingw32 Here they are:

On Wednesday 11 March 2009 15:47, Török Edwin wrote: > > Go to http://google1.osuosl.org:8080 and have a look. > > Looks like the x86_64 buildsbots are failing: > > /.AUTO/cray/iss.compiler/cost/tools/llvm-tools/x86_64-unknown-linux-gnu/bin >/../lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../x86_64-unknown-linux- >gnu/bin/ld: >

On 2009-03-06 22:18, David Greene wrote: > Thanks to Daniel, we have a new home for the validator buildbot. Thanks, > Daniel! > > Go to http://google1.osuosl.org:8080 and have a look. > Looks like the x86_64 buildsbots are failing:

On Wed, Oct 21, 2009 at 10:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Óscar Fuentes wrote: >> >> 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:

Hi Daniel, I am executing some test cases on one of the slave and got the following output on stdio screen. "command timed out: 1200 seconds without output" Some of my test cases executes for (~1 hr) and won't display any output on stdio screen. So is there anyway to increase the timeout value to 1 hour or so. PC details are as follows: Linux Box(2.6.29) with buildbot version

On 2009-10-21 20:14, Óscar Fuentes wrote: > 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

LLVMers, If you're not working from the CVS "head", you can ignore this. Otherwise, please read it! I have committed changes to CVS head that require changes to your build environment. This is part of PR432. The changes involve getting the CFE to build an executable named llvm-gcc instead of gcc. The hyphenated name was chosen to be consistent with other LLVM tools, it is also

Since at least yesterday afternoon, the Google buildbot server has been broken. The top-level page (http://google1.osuosl.org:8011/) works fine, but all the links from there (e.g., http://google1.osuosl.org:8011/waterfall) result in "can't connect to server" errors. Can someone please fix it?

Hello everyone, Zorg is a common code for multiple different buildbot setups. This is why it sits in its own subtree. The only tricky thing there is that it assumes some relative position of zorg and master setup. Documenting this would save somebody some time. All together wasn't a problem so far. But having a better documentation and a set of files for a simple local setup is a good idea.

Hello everyone, I am going to remove these two existing llvm-gcc cross builders: http://google1.osuosl.org:8011/builders/llvm-gcc-x86_64-darwin10-self-mingw32 http://google1.osuosl.org:8011/builders/llvm-gcc-x86_64-darwin10-cross-mingw32 These configurations gets built as parts of the build build-self-4-mingw32 does, so we don't loose anything just getting the same result a bit slower,