similar to: [Buildbots] - Looking for help with new 32 bit Windows buildbot

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)

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

How about tweaking the compiler-rt cmakefiles so that if lsan is not supported, the target check-lsan still exists but does nothing? I've attached a patch that does this. (I don't know much about cmake so there might be a better way of doing it.) Alternatively, can I change the zorg build script so that "run sanitizer tests in gcc build" doesn't try to run check-lsan etc

Our Flang-aarch64 buildbots just won't connect to the main Buildbot master anymore. I switched them to the staging buildbot master instead and it seems fine for now. Is there anything that we can/should tweak at our end? http://lab.llvm.org:8014/#/waterfall?tags=flang -Andrzej On 08/10/2020 00:31, Galina Kistanova via cfe-dev wrote: > They are online now -

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

It looks like dragonegg should have a single buildbot using gcc 4.7. All others would be with 4.6 and 4.5. All the 4.5 and 4.6 ones went red since we reject those compilers now. The 4.7 one is trying to use gcc13, which is currently offline so we now have 0 bot coverage for dragonegg. Can we drop the 4.5 and 4.6 bots and reuse one of the manchines for 4.7? Is there documentation somewhere on how

On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think having -Werror bots is a good idea, at least when self hosting. > Non-self-hosting -Werror (i.e. with older versions of Clang, or with GCC, > etc.) might also be useful, but I'm less sure (since we can't fix those > warnings if the warning is the problem). On Tue, Mar

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

Hi, Currently the first stage ("run sanitizer tests in gcc build") of the sanitizer-ppc64-linux1 buildbot is only failing because of: + cd clang_build + make -j16 check-lsan make: *** No rule to make target `check-lsan'. Stop. + echo @@@STEP_FAILURE@@@ @@@STEP_FAILURE@@@ + cd clang_build + make -j16 check-msan make: *** No rule to make target `check-msan'. Stop. + echo

Hi Asiri, You can use your local master for this or use silent master. Silent buildbot is currently copy of llvm buildbot, but does not sent any notifications. The both have the same set of builders and it's easy to switch a slave between them. To add slave/builder please add your slave and builder to zorg, but point your slave to silent master: use lab.llvm.org:9994 instead of

I just changed this build on green dragon to warn and email if warnings are found in the console log: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_build/ > On Mar 22, 2016, at 6:24 PM, David Jones via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at

Hi Paula, This error is fine. The buildbot has tested the worker version. 0.8.x apparently does not have that method. The error gets handled gracefully on the server side. At least it seems so so far. That should not prevent your bot from connecting. Thanks Galina On Thu, Oct 8, 2020 at 2:11 PM Paula Askar <paulatoth at google.com> wrote: > Hey Andrzej, > > What are you seeing

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

It looks like all sanitizer builder are still offline http://lab.llvm.org:8011/#/builders On Tue, 6 Oct 2020 at 00:34, Galina Kistanova via cfe-commits < cfe-commits at lists.llvm.org> wrote: > Hello everyone, > > The staging buildbot was up and running for 6 days now, and looks good. > > Tomorrow at 12:00 PM PDT we will switch the production buildbot to the new >

On Wed, Jul 31, 2019 at 11:37 AM Vitaly Buka via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I have no idea how. > Are there particular problems? Now it should be quite. > Console has a bunch of stale builders which are even less useful. > LLVM has a silent build master that does not send email. When Nico added the gn build, apparently we promised not to set up builders

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

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

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

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