search for: osuosl

...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 > `/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 included from > /home/buildslave/zorg/buildbot/osuosl/slave/cla...

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 included from /home/buildslave/zorg/buildbot/osuosl/slave/clang-native-arm-cortex-a9/l...

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

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

...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 >> `/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 included from >> /home/buildslave/zorg/build...

...d 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: http://google1.osuosl.org:8011/builders/llvm-arm-linux/builds/754 - Revision: 128836 last successful ARM build by the builder http://google1.osuosl.org:8011/builders/llvm-arm-linux/builds/755 - Revision: 128851 failed build http://google1.osuosl.org:8011/builders/llvm-arm-linux/builds/756 - Revision: 128873 failed 2010-...

...linux/builds/197 The odd thing is that I can't see any suspicious looking commits. Does anyone have any suggestions? Here are what the failures look like: (1) llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td 0 llvm-tblgen 0x0818937b Stack dump: 0. Program arguments: /home/baldrick/osuosl/slave/llvm-gcc-i386-linux-selfhost/llvm.obj.2/Release+Asserts/bin/llvm-tblgen -I /home/baldrick/osuosl/slave/llvm-gcc-i386-linux-selfhost/llvm.src/lib/VMCore -I /home/baldrick/osuosl/slave/llvm-gcc-i386-linux-selfhost/llvm.src/include -I /home/baldrick/osuosl/slave/llvm-gcc-i386-linux-selfhost/l...

...n.com/> On Nov 18, 2011, at 11:49 AM, Galina Kistanova wrote: Author: gkistanova Date: Fri Nov 18 13:49:26 2011 New Revision: 144978 URL: http://llvm.org/viewvc/llvm-project?rev=144978&view=rev Log: Change configure for builder clang-native-arm-cortex-a9. Modified: zorg/trunk/buildbot/osuosl/master/config/builders.py Modified: zorg/trunk/buildbot/osuosl/master/config/builders.py URL: http://llvm.org/viewvc/llvm-project/zorg/trunk/buildbot/osuosl/master/config/builders.py?rev=144978&r1=144977&r2=144978&view=diff ==============================================================...

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 "/usr/lib/python2.7/dist-packages/twisted/internet/def...

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 failure of llvm-i686-linux on llvm. Full details are available...

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

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

...37 clang 0x000000000063c268 cc1_main(char const**, char const**, char const*, void*) + 920 38 clang 0x0000000000645f77 main + 7079 39 libc.so.6 0x00002aaaab8b7c4d __libc_start_main + 253 40 clang 0x0000000000639ad9 Stack dump: 0. Program arguments: /home/baldrick/osuosl/slave/clang-x86_64-debian-fnt/llvm.obj/Release+Asserts/bin/clang -cc1 -triple x86_64-pc-linux-gnu -emit-llvm -disable-free -main-file-name slib.c -mrelocation-model static -masm-verbose -mconstructor-aliases -munwind-tables -target-cpu x86-64 -momit-leaf-frame-pointer -coverage-file Output/slib.ll...

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

...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 llvm.org or the local machine, not any particular commit. - Daniel > -----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 failure of llvm-i686-linux on llvm...

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) 'zorg' is expected to be located on $(HOME)/zorg. 2012/11/16 Hongbin Zheng <etherzhhb at gmail....

...ova 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 >>> `/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 included from >>> /home/b...

...n(char const**, char > const**, char const*, void*) + 920 > 38 clang 0x0000000000645f77 main + 7079 > 39 libc.so.6 0x00002aaaab8b7c4d __libc_start_main + 253 > 40 clang 0x0000000000639ad9 > Stack dump: > 0. Program arguments: > > /home/baldrick/osuosl/slave/clang-x86_64-debian-fnt/llvm.obj/Release+Asserts/bin/clang > -cc1 -triple x86_64-pc-linux-gnu -emit-llvm -disable-free > -main-file-name slib.c -mrelocation-model static -masm-verbose > -mconstructor-aliases -munwind-tables -target-cpu x86-64 > -momit-leaf-frame-pointer -coverage-...

We want to switch running our slave bot with clang/llvm instead of gcc. We have the following proposed patch. We can't test this in our environment but will monitor and adjust if there are issues. svn co http://llvm.org/svn/llvm-project/zorg/trunk zorg mips-builder.patch Index: buildbot/osuosl/master/config/builders.py =================================================================== --- buildbot/osuosl/master/config/builders.py (revision 203958) +++ buildbot/osuosl/master/config/builders.py (working copy) @@ -90,6 +90,8 @@ 'builddir':"llvm-mips-linux",...

Hi Danny, On Fri, Sep 17, 2010 at 9:13 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > Can't offer it in the bay area, but i can offer space in oregon state > university (which is where the osuosl machines reside). > http://osuosl.org/services > > Why do you need access if you have people willing to handle support > tickets and remote console/power control cards? I don't, really. To be honest, I wasn't aware that OSUOSL had all of these services available. > I have y...