similar to: [LLVMdev] Documentation for adding builders and slaves to zorg?

On 04/08/2014 16:20, Dmitri Gribenko wrote: > On Mon, Aug 4, 2014 at 2:20 PM, Dan Liew <dan at su-root.co.uk> wrote: >>>> Second, is there a simple way to test the builder and config before I >>>> commit >>>> it? >>> >>> I am afraid not. >>> >> >> But there is a ugly (and certainly not simple) way to partially test

> > Second, is there a simple way to test the builder and config before 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

Hello Marco, Welcome aboard! slaves.py keeps the build slaves definitions, builders.py keeps the builders definitions. You have to have both. The steps of adding a new slave is here: http://llvm.org/docs/HowToAddABuilder.html. Please make sure you done the step # 10 before bringing your slave up, otherwise it wouldn't be authorized by the master and will be blacklisted after multiple

Hello everyone, We are in the middle of porting the majority of zorg to GitHub/monorepo. The following build factories will be ported and if you use one of those for your bots, you are all covered: * ClangBuilder.getClangCMakeBuildFactory (31 bots) * ClangBuilder.getClangCMakeGCSBuildFactory (2 bots) * LibcxxAndAbiBuilder (23 bots) * SphinxDocsBuilder (7 bots) * UnifiedTreeBuilder (11

Thank you. Alexei just committed the change to SVN. Regards, Marco Leogrande Sent by a carbon-based life form; hence, it may contain repetitions, inaccuracies, logical fallacies and repetitions. On Wed, Jun 17, 2015 at 2:52 PM, Galina Kistanova <gkistanova at gmail.com> wrote: > LGTM. > Please commit. > > Thanks > > Galina > > On Tue, Jun 16, 2015 at 8:32 PM,

Galina, thanks again for your help. I have cooked a new patch that should make a bit more sense. I have added the new builder under _get_experimental_scheduled_builders(), as the comment above that function suggested me it would be a good idea. :) Does it look a reasonable start? Regards, Marco Leogrande Sent by a carbon-based life form; hence, it may contain repetitions, inaccuracies,

Hi everyone, I am working with Alexei Starovoitov to contribute an LLVM buildbot for the 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

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 >

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

Yeah. That code has been there since r91421 and wouldn't have failed recently otherwise. Did something change on the host? -eric On Sep 20, 2011, at 11:27 AM, Jim Grosbach wrote: > 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 : >>

Hello build bot owners! The staging master is ready. Please feel free to use it to make sure your bots would work well with the monorepo and github. The following builders could be configured to build monorepo: * clang-atom-d525-fedora-rel * clang-native-arm-lnt-perf * clang-cmake-armv7-lnt * clang-cmake-armv7-selfhost-neon * clang-cmake-armv7-quick * clang-cmake-armv7-global-isel *

Hi Galina, It seems that our libcxx bots are now triggering builds for any changes to llvm: http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux/builds/2434 Should I file a bug report for this? Thanks, Diana On Sat, 19 Oct 2019 at 11:36, Galina Kistanova via cfe-commits <cfe-commits at lists.llvm.org> wrote: > > Hello everyone, > > The staging master is

Galina, Looks like the build bots have frozen. Expected? Joe Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 jabbey at arxan.com<mailto:jabbey at arxan.com> www.arxan.com<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

Hello everybody, I want to put some kind of instruction on how to add new slave to llvm master. I think it should be somewhere on llvm.org, but not sure on exact place. Any comments/suggestions will be appreciated. Thanks Galina If you want to add your build configuration to the LLVM buildbot infrastructure. 1. Check the existing build configurations to make sure the one you are

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

I was hoping to avoid the trouble of having to setup a master buildbot. But may be it's just easier to run Zorg as-is locally alongside the buildslave. I'll give that a go. Cheers, / Asiri On Fri, May 27, 2016 at 8:45 PM, Yaron Keren <yaron.keren at gmail.com> wrote: > You don't really need to use the llvm builders infrastructure, just setup > a local jenkins (or

The document here explains pretty well how to add a buildslave to the buildbot: http://llvm.org/docs/HowToAddABuilder.html However, it's not clear to me how to add a new build config. I would like to add a buildslave that builds with -Werror so we can catch and correct warnings early. How should I go about adding a new build configuration? Do I edit one of the .py files in zorg? Thanks!

I think what she is referring to was that the build seemed to be triggered by a commit to a project that shouldn't trigger builds on a libcxx bot (i.e. the change was in llvm). I have a somewhat orthogonal but related question. In the past, commits to compiler-rt did not trigger builds on llvm/clang/sanitizer bots. Has this behaviour been rectified with the move to github? I am really sorry

Dmitri Gribenko <gribozavr at gmail.com> writes: > On Tue, Jan 15, 2013 at 2:43 AM, <greened at obbligato.org> wrote: >> The document here explains pretty well how to add a buildslave to the >> buildbot: >> >> http://llvm.org/docs/HowToAddABuilder.html >> >> However, it's not clear to me how to add a new build config. I would >> like