similar to: [LLVMdev] FW: buildbot failure in llvm on llvm-i686-linux

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

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

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

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:

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 >

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 Sun, Aug 9, 2009 at 1:04 PM, Óscar Fuentes<ofv at wanadoo.es> wrote: > Eli Friedman <eli.friedman at gmail.com> writes: > >> On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote: >>> I think most LLVM users on Windows are interested on X86 only. This >>> saves a lot of time on the build process and creates smaller >>>

I am unable to connect to build master at:google1.osuosl.org:9990 from my buildslave. See attached twisted9.0.0 log. 2010-02-12 09:50:03-0800 [-] Log opened. 2010-02-12 09:50:03-0800 [-] twistd 9.0.0 (C:\Python26\python.exe 2.6.2) starting up. 2010-02-12 09:50:03-0800 [-] reactor class: twisted.internet.win32eventreactor.Win32Reactor. 2010-02-12 09:50:03-0800 [-] Starting factory

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

Am 09.08.09 23:36, schrieb Eli Friedman: > > MSVC *is* continuously checked; see > http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone > who breaks the MSVC build will get a nastygram from buildbot. > Please note that the MSVC buildbot only builds the X86 target at the moment. I don't know why though.

Eli Friedman <eli.friedman at gmail.com> writes: > MSVC *is* continuously checked; see > http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone > who breaks the MSVC build will get a nastygram from buildbot. This is new news for me. If the developer who broke the msvc build receives a nastygram, would he urged to fix it when he has no msvc compiler and probably no

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

On Sun, Aug 9, 2009 at 3:35 PM, Óscar Fuentes<ofv at wanadoo.es> wrote: > Eli Friedman <eli.friedman at gmail.com> writes: > >> MSVC *is* continuously checked; see >> http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9.  Anyone >> who breaks the MSVC build will get a nastygram from buildbot. > > This is new news for me. > > If the developer

On Mon, Nov 3, 2008 at 2:43 AM, Duncan Sands <duncan.sands at math.u-psud.fr> wrote: > Hi Daniel, > >> 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). > >

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:

Hi Galina, > LLVM buildmaster is up and running as lab.llvm.org:8011. ... > Buildslave owners, please contact me directly with your new passwords > and I'll update the master as soon as I can. should build slaves now use the osuosl configuration? For example osuosl/Config.py has def getBuildmasterHost(): return 'google1.osuosl.org' which is surely wrong now. On

Hello Daniel, osuosl build master (google1) is moved to another place or just down? Thanks Galina

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