similar to: [LLVMdev] is there a script for recursing the compiler?

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

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

Okay. Cool. So do you bootrstrap and verify as part of the usual testing? Do the nightly scripts do this? Reed On 06/28/2012 11:08 AM, Eric Christopher wrote: > On Jun 27, 2012, at 10:48 PM, Reed Kotler<rkotler at mips.com> wrote: > >> On 06/27/2012 05:00 PM, Eric Christopher wrote: >>> On Jun 19, 2012, at 5:24 PM, reed kotler<rkotler at mips.com> wrote:

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

On 06/27/2012 05:00 PM, Eric Christopher wrote: > On Jun 19, 2012, at 5:24 PM, reed kotler<rkotler at mips.com> wrote: > >> Do the llvm nightly scripts "recurse" the compiler or just test that it >> can self host itself? >> > No idea what you mean here. Can you explain? > > -eric recursing a compiler means this. clang/llvm source == src compile

On Jun 27, 2012, at 10:48 PM, Reed Kotler <rkotler at mips.com> wrote: > On 06/27/2012 05:00 PM, Eric Christopher wrote: >> On Jun 19, 2012, at 5:24 PM, reed kotler<rkotler at mips.com> wrote: >> >>> Do the llvm nightly scripts "recurse" the compiler or just test that it >>> can self host itself? >>> >> No idea what you mean

There as been a bit of talk about zorg recently, so I thought this would be a good time to share our plans for the darwin buildbots that live here: http://lab.llvm.org:8013/builders <http://lab.llvm.org:8013/builders> To be clear, those are not these buildbots: http://lab.llvm.org:8011/builders <http://lab.llvm.org:8011/builders> We are not talking about changing the main

Do the llvm nightly scripts "recurse" the compiler or just test that it can self host itself?

On Jun 19, 2012, at 5:24 PM, reed kotler <rkotler at mips.com> wrote: > Do the llvm nightly scripts "recurse" the compiler or just test that it > can self host itself? > No idea what you mean here. Can you explain? -eric

Hello everyone, The buildbot upgrade is entering the phase when the results to become visible. No change is required at this time on any of the builders. The bot owners could upgrade the buildbot on build computers later, at their convenience, as this is not on the critical path. We are going to upgrade the staging bot first. Then, once that is stable and all detected issues are resolved, we

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

Eric Christopher <echristo at apple.com> writes: > On Jun 19, 2012, at 5:24 PM, reed kotler <rkotler at mips.com> wrote: > >> Do the llvm nightly scripts "recurse" the compiler or just test that it >> can self host itself? >> > > No idea what you mean here. Can you explain? Step 1: compile Clang with some other compiler (i.e. gcc or old

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 >

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

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 -

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

Hello everyone, It might make sense to start from rebooting the buildmaster, just to make sure everything is all right on this end. Yesterday I have tried to apply the latest changes from zorg and some of them are broken. Theoretically, checkconfig shouldn't affect the working instance, but the reality could be different... I planned to rollback to the last known-to-be-good revision and

is test-suite being run still by itself (independent of llvm)? if so, are there public build bots for this? is lnt going to replace test-suite as the normal mechanism for running test-suite? Tia. Reed

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.