similar to: [LLVMdev] Please fix the buildbots.

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:

Ó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

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

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

Hello everyone, LLVM buildmaster is up and running as lab.llvm.org:8011. Daniel Berlin is working on getting the current buildslave passwords from the old buildmaster, but this may not be possible. I'd suggest changing buildslave passwords anyway, just in case. Buildslave owners, please contact me directly with your new passwords and I'll update the master as soon as I can. Thanks

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

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

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? > > We were wondering what kind of support we could give to make sure ARM > code is correct and don't regress, specially before

Hi all, 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? We were wondering what kind of support we could give to make sure ARM code is correct and don't regress, specially before releases (I know it's a bit late

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

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:

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

Hello everybody, Just a short note that clang build "clang-native-arm-cortex-a9" is broken and the very last successful build was for revision 139932. All newer revisions fail. The builder is available here: http://172.16.0.135:8011/waterfall Thanks Galina

The host c++ standard library is missing <utility>, it appears. On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > Please use the correct link : > http://63.145.236.72:8011 > and ignore the previous. > > Also log for broken build is here: > > make[1]: Entering directory >

Hey Alexey, This bot has been failing for a week, by the looks of it - what's the deal? On Thu, May 7, 2015 at 7:31 PM, <llvm.buildmaster at lab.llvm.org> wrote: > The Buildbot has detected a new failure on builder sanitizer-x86_64-linux > while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/17810 >

All, This buildbot is getting lots of assertion failures in the test suite. They were probably caused by my commit: ------------------------------------------------------------------------ r151049 | foad | 2012-02-21 09:25:52 +0000 (Tue, 21 Feb 2012) | 6 lines Changed paths: M /llvm/trunk/lib/VMCore/LLVMContextImpl.h M /llvm/trunk/lib/VMCore/Type.cpp PR1210: make uniquing of struct and

Please use the correct link : http://63.145.236.72:8011 and ignore the previous. Also log for broken build is here: make[1]: Entering directory `/home/buildslave/zorg/buildbot/osuosl/slave/clang-native-arm-cortex-a9/llvm/lib/Support' llvm[1]: Compiling APFloat.cpp for Release+Asserts build llvm[1]: Compiling APInt.cpp for Release+Asserts build In file included from APFloat.cpp:15: In file