similar to: Wanted: a way to test changes before breaking all the build bots.

> On Oct 9, 2019, at 7:23 AM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Apple moved all their bots to a Green Dragon CI system years ago: http://green.lab.llvm.org/green/ <http://green.lab.llvm.org/green/> > > (yeah, it'd be nice if the project wasn't split between two CI systems) If someone is really bored, it would be a cute project

Hi, as far as I can tell the only mac bot on http://lab.llvm.org:8011/console is http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/37511 which only runs "check-lld". lld is probably the only tool in the LLVM / clang repos that's not widely used on macOS. What happened to the mac bots that run check-clang, check-clang-tools, check-clangd, check-llvm, and so on? Nico

Hi Galina, It seems that all the bots (buildbots and green dragon) are not processing new SVN revisions since the llvm.org IP address update. It seems we have gotten no new revs since Noon today? Perhaps the SVN mirror is not picking up new commits?

Hi, many of the bots on http://lab.llvm.org:8011/console don't do anything in their compile phase, even if they should. For example, these bots all don't do anything in their compile phase in any builds, even if they should: http://lab.llvm.org:8011/builders/clang-x64-ninja-win7/ http://lab.llvm.org:8011/builders/clang-ppc64be-linux

Hi, It seems the problem is that the bot is updating llvm.src, but trying to build from llvm. Galina, it looks like this is related to your recent changes to zorg, you probably missed a spot somewhere and I can't find it on a first glance. Could you have a look? Thanks, Diana On 5 September 2016 at 12:01, Diana Picus <diana.picus at linaro.org> wrote: > Hi Nico, > > Thanks

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

> On Oct 7, 2015, at 3:28 PM, Renato Golin <renato.golin at linaro.org> wrote: > > On 7 October 2015 at 23:20, Chris Matthews <chris.matthews at apple.com> wrote: >> For instance, a build that fails with a ninja error, will say so, same with a >> svn failure or a Jenkins exception. > > Will these get mailed to developers? Or admins? Unfortunately, Jenkins

On 10.12.2012, at 15:19, Ulrich Weigand <Ulrich.Weigand at de.ibm.com> wrote: > 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

Benjamin Kramer <benny.kra at gmail.com> wrote on 11.12.2012 12:48:55: > On 10.12.2012, at 15:19, Ulrich Weigand <Ulrich.Weigand at de.ibm.com> wrote: > > Maybe I'm confused somehow, but I thought this one: > > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2 > > does bootstrap and then run both LLVM and Clang tests (successfully): > >

Hi all, It seems some of the test-suite bots are red because they can't find the six module anymore. See e.g. http://lab.llvm.org:8011/builders/clang-cmake-aarch64-quick/builds/6867 http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/5727 Does anyone know how to fix this? Thanks, Diana -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, There was a new Python setuptools release (36.0.0) today, that caused this compatibility issue. The suggestion to stop breaking the builds is to add a static setuptools version on lnt's requirements.client.txt. The latest known compatible version is 35.0.2. I have tested it building a LNT sandbox and it seems to works. setuptools==35.0.2 I'll create a bug on LNT so we can

r223478 seems to be responsible for PR21770: http://llvm.org/bugs/show_bug.cgi?id=21770 On Fri, Dec 5, 2014 at 3:10 PM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > I'm not sure if it helps but the clang builder for mips has been dying of > timeouts since > http://lab.llvm.org:8011/builders/clang-cmake-mips/builds/389 which only > has one commit in the blamelist

Folks, I'm not sure what happened, but some commit in this build made Clang run forever on ARM: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/2203 The missing commits are to the sanitizers and they are not even checked out on this bot, so I don't think it has anything to do with that. It's also unlikely to be something on the Hexagon back-end, since all changes are

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

Can we unlist defunct builders? For example, none of the bots running on the dunbar1 slave have been building for months. They just clutter up the waterfall view. Cameron

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

Hi, I have Asterisk set up on Fedora with a single SIP trunk, with a few handsets configured. The Asterisk box has both public and private addressing, so "canreinvite=no" is set on both the SIP trunk and handset configurations so I can get around the nasty NAT issues. One odd behaviour I am seeing is certain destinations are resulting in different SIP codes being sent back to Asterisk,

One strategy I use for our flaky bots is to have them email me only. If the failure is real, then I forward the email to who ever I find on the blame list. For a flaky build, this is least you can do. For our flaky builds I know how and why they are flaky, some person that gets email does not. This is also a great motivator to help me know what is wrong, and how to fix it. By default, all new

As a complete newcomer I am attempting to learn to use R, but am finding it extremely difficult because I have not yet found an "Introduction to R". For over a week now I have monitored the R-help list, studied the R-FAQ and related documents, downloaded and run the Windows R and looked at the Help, downloaded early and late samples of the R-help archives, and searched for illuminating

It looks like the bots are still red? — Adrian > On Nov 10, 2017, at 3:14 PM, Zachary Turner <zturner at google.com> wrote: > > Wasn't quite fixed, but it got a lot further this time. This time there was still an issue in the test_debuginfo.pl <http://test_debuginfo.pl/> script regarding a hardcoded path to the llgdb.py script. I think I never encountered this locally