similar to: [LLVMdev] Trouble starting private llvm buildbot master.

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)

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

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

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 >

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

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

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 better documentation and a set of files for a simple local setup is a good idea.

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 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 from my perspective. There

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

On Thu, Jan 3, 2013 at 1:52 PM, Renato Golin <renato.golin at linaro.org> wrote: > 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? That's how you achieve this goal.

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

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:

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 *

We're thinking about running our own buildbot against the upstream llvm and clang sources. I'm talking to our build folks and seeing what they can allow. Maybe we can contribute some build slaves to the osuosl buildbot but I'm not sure. If we do end up having to run our own buildbot, what's the best way to integrate that into the upstream web page and status notifier? Basically,

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

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

> On Feb 3, 2017, at 12:45 PM, Dylan McKay via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The builder isn’t marked as experimental so I think the expectation is that people keep it green and contact the bot owner if they need help figuring out why their change makes it red. That said, it sounds a bit odd to have a non-experimental builder for an experimental backend. >

I don't see any problem mangling it to be honest even though there seems to be only one prototype anyways. We could add restrict in as well. Cheers, Anastasia ________________________________ From: Hongbin Zheng <etherzhhb at gmail.com> Sent: 17 September 2016 05:32:54 To: Liu, Yaxun (Sam) Cc: cfe-dev at lists.llvm.org; llvm-dev; Bader, Alexey (alexey.bader at intel.com); Anastasia