search for: zorg

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

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

...s 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 > `/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/...

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

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

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

...m<http://www.arxan.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 all, I'm working on adding a new buildbot. I'm don't understand what is required when patching zorg's builders.py and slaves.py. Is there any documentation on this? Would anybody be willing to help? Best, Eric Fiselier -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140731/93c86c1a/attachment.html&gt...

...gt; 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/build...

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

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

...fore I commit > > it? > > I am afraid not. > But there is a ugly (and certainly not simple) way to partially test the builder that I mentioned recently [1]. I say partially because I ended up removing all the builders apart from my own. @Dmitri - Has anyone considered reorganising zorg so it is easier to test a builder locally? [1] http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-August/075287.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140804/902de825/attachment.html>

Hi all, I'm trying to add builders to zorg for libc++ and libc++abi. I think I have the builder right, but I have a few questions. First, how do I know which build slaves to use? Is it okay to just pick a few, is there some policy defining which are fair game, or do I need to add a new one? Second, is there a simple way to test the builde...

...o build stage1 and using > Werror. > > Certainly, we tend to fix warnings even from earlier Clang versions and > from GCC in order to keep Werror clean. > I've dug around a bit, and it looks to me like separating phase1 and phase2 behavior is going to be a bit tricky (looking at zorg [*]) as long as we want -Wno-error as the default for buildbots. So, the first thing I would propose is to add this buildbot and run it for a while, just to see what the current background rate of breakages will be. I think getting a feel for the baseline is going to be a solid first step. If tha...

On 3 January 2013 21:53, David Blaikie <dblaikie at gmail.com> wrote: > That's how you achieve this goal. What a buildbot does is governed by > the configuration in the zorg repository (that's where we keep the > buildbot configuration code that is sync'd up to the lab.llvm.org > buildmaster). > Hi David, I had a go at Zorg after the website was back online. As far as I can tell, buildbot/osuosl/master/config/builders.py is the script that has to be...

...se to build stage1 and using Werror. > > Certainly, we tend to fix warnings even from earlier Clang versions and from GCC in order to keep Werror clean. > > I've dug around a bit, and it looks to me like separating phase1 and phase2 behavior is going to be a bit tricky (looking at zorg [*]) as long as we want -Wno-error as the default for buildbots. > > So, the first thing I would propose is to add this buildbot and run it for a while, just to see what the current background rate of breakages will be. I think getting a feel for the baseline is going to be a solid first ste...

...a ugly (and certainly not simple) way to partially test the >> builder that I mentioned recently [1]. > > Nice write-up! > >> I say partially because I ended up removing all the builders apart from my >> own. >> >> @Dmitri - Has anyone considered reorganising zorg so it is easier to test a >> builder locally? > > I am not aware of such effort. However, it would be great to be able > to easily set up a buildmaster locally. This will probably facilitate > further refactorings of zorg code. Currently developers tend not to > touch it bec...

On 3 January 2013 21:29, David Blaikie <dblaikie at gmail.com> wrote: > Fair enough - you could write up a patch for the zorg repository to do > this. > Wouldn't requiring every buildbot to use LNT achieve the same thing? --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130103/47cb78d9/attachment.html>

Hello everyone, Zorg upgrade to a recent version of buildbot is coming. We would do our best to make the transition as smooth and transparent to the majority of LLVM community, as possible. The process will be handled similar to how we did the github transition. As the next step, we will be cleaning zorg. All the co...

...experimental BPF backend. I am following the steps at [1] to setup a buildbot and I was mostly successful: I was able to setup a slave and a temporary master to check its base config. Now I'm not sure about the next step: patching the "slaves.py" and "builders.py" files in zorg. * Is there a guide I can follow to understand the format of these files? For example, being BPF an experimental backend, I need to provide extra parameters to cmake at build time. * Also, is there a way to test these changes in zorg in a local environment before submitting the patch for review?...