similar to: Zorg migration to GitHub/monorepo

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

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

Hi Richard, Marco, I noticed that you two are the remaining bot owners using the `getClangBuildFactory` from `ClangBuilder`. All the other bots using that builder have moved to the new `getClangCMakeBuildFactory`, including Windows ones. Given that they do similar functionalities, I'd like to encourage you to move to the new factory, so that we can simplify the builder's code. Thanks!

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

On 6 February 2013 16:00, David Tweed <david.tweed at arm.com> wrote: > Looking at the output from the a15 buildbot it looks like you are choosing > to do a "make clean". > I'm not choosing, this is the default "Clang" run. ;) If more people feel inclined to change the Clang build on all buildbots to use CMake / Ninja, I'm up for it, too. Galina, have

On 28 May 2014 17:44, Justin Bogner <mail at justinbogner.com> wrote: > In the autoconf system, I'm pretty sure compiler-rt's build is triggered > by a Makefile in clang, tools/clang/runtime/compiler-rt/Makefile. This > Makefile comments "We currently only try to generate runtime libraries > on x86", so I guess that's the place to start if you want to get it

Chandler Carruth <chandlerc at gmail.com> wrote: > I've been working to revive the PPC64 build bots, and succeeded, but > not for the right reasons. There were still bootstrap assertion > failures and other pretty blatant errors. Then we figured out why: > the Clang bootstrapping build bots for Power7 are not actually > running any of the Clang tests! > > Could one

Hey Galina, Will; I've been working to revive the PPC64 build bots, and succeeded, but not for the right reasons. There were still bootstrap assertion failures and other pretty blatant errors. Then we figured out why: the Clang bootstrapping build bots for Power7 are not actually running any of the Clang tests! Could one of you tweak this build bot's configuration to match the other

Folks, I realised there's a "checkout_compiler_rt" option on ClangBuilder, which does checkout the sources, but couldn't build them on ARM. I also don't build them during releases (yet) because the configure script doesn't prepare the Makefiles for compiler-rt. A while ago I got it running on ARM with CMake files, but since these are buildbots, I'm not sure

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

Renato, thanks for the heads-up. For clang-bpf-build the change should be trivial since we don't use a fancy configuration. I have attached the patch, please apply if appropriate. Thanks. Regards, Marco Leogrande Sent by a carbon-based life form; hence, it may contain repetitions, inaccuracies, logical fallacies and repetitions. On Mon, Oct 31, 2016 at 5:14 AM, Renato Golin

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

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

On Tue, Jan 15, 2013 at 7:07 PM, <dag at cray.com> wrote: > 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 >>>

My thought was that its reasonable to expect no warnings when building from bootstrap (as you say) and the last release of Clang. Generally, I think we should work around warnings in the last release of Clang if only for the convenience of folks using that release to build stage1 and using Werror. Certainly, we tend to fix warnings even from earlier Clang versions and from GCC in order to keep

Dmitri Gribenko <gribozavr at gmail.com> writes: > On Tue, Jan 15, 2013 at 7:07 PM, <dag at cray.com> wrote: >> 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:

Hi, I'm trying to set up a self-host ARM bot and am following the ClangBuilder with two stages, copying the config from other bots, but I can't find my way around the configure options... This is my config: ## Cortex-A9 check-all self-host {'name': "clang-native-arm-cortex-a9-self-host", 'slavenames':["linaro-panda-02"],

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

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