similar to: [LLVMdev] All bots are down

On 13 October 2015 at 22:28, don hinton <hintonda at gmail.com> wrote: > However, the build that failed thought it needed to do 106 steps. It hung > on the 83 that didn't exist. Interesting... > Could this be a cmake/ninja issue? It could. Those bots are not cleaning between builds (or it would take hours). If that's what's happening, I'll have to re-think my

I don’t have access to that server. I have been using a cloud LNT instance for the performance runs on the green-dragon cluster. So far it has provided 100% uptime! http://llvm-lnt.herokuapp.com <http://llvm-lnt.herokuapp.com/> > On Nov 24, 2014, at 3:24 PM, Tobias Grosser <tobias at grosser.es> wrote: > > On 24.11.2014 23:54, Galina Kistanova wrote: >> Hello

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

git 2.7.4 was released 17-Mar-2016. https://mirrors.edge.kernel.org/pub/software/scm/git/ Here is the git downloads page. https://git-scm.com/downloads Neil Nelson On 10/14/19 1:56 AM, Diana Picus via llvm-dev wrote: > Hi Galina, > > Thanks for the heads up. > > On Fri, 11 Oct 2019 at 21:09, Galina Kistanova via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >>

This issue is back: FNT bots are reporting success in spite of tests failing, and the "report" text is empty again. Did someone change something? Ciao, Duncan. On 12/12/12 07:53, Duncan Sands wrote: > On 11/12/12 23:16, Galina Kistanova wrote: >> The problem remains after the buildmaster restart. > > The FNT builders are now all failing again, and the "report"

On 7 October 2015 at 22:14, Eric Christopher <echristo at gmail.com> wrote: > As a foreword: I haven't read a lot of the thread here and it's just a > single developer talking here :) I recommend you to, then. Most of your arguments are similar to David's and they don't take into account the difficulty in maintaining non-x86 buildbots. What you're both saying is

Hello all, I broke the build, but I did not receive any blame email about it. I have a feeling the blame emails are not working. Is anyone experiencing the same thing? Could it be related to the last-week master restart (which seems to have reset build numbers as well)? regards, pl

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 -

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

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

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 Feb 24, 2015, at 8:45 AM, Tobias Grosser <tobias at grosser.es> wrote: > > On 09.02.2015 20:12, Chris Bieneman wrote: >> It came up on another thread that our current minimum required CMake version 2.8.8, has some bugs that cause issues when building with MSVC + Ninja, and one potential solution was to raise the minimum required version of CMake. >> >> CMake

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 David/Galina, FYI, I found one big reason why self-hosting bots fail long after the offending commit is tested: dirty builds. In a dirty build (no make clean), when a file X is changed that breaks file Y, the bot will only accuse the failure when file Y is changed, too, so that stage1 with modified X will compile file Y, and break. At hindsight, it's obvious. But I hadn't connected

Thanks, Galina. It doesn't explain why the test worked on some bots but not this one, but Justin's workaround is okay with me. --paulr From: Galina Kistanova [mailto:gkistanova at gmail.com] Sent: Thursday, November 09, 2017 10:09 AM To: Robinson, Paul Cc: Davide Italiano; llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] Problem with 'sed' on one Windows bot? There is nothing

Hi Folks, Looks like our LNT ARM buildbot with the vectorizer is running and producing good results. There are only 11 failures: FAIL: MultiSource/Applications/Burg/burg.execution_time (1 of 1104) FAIL: MultiSource/Applications/ClamAV/clamscan.execution_time (2 of 1104) FAIL: MultiSource/Applications/lemon/lemon.execution_time (3 of 1104) FAIL:

On 19 February 2013 15:16, Arnold Schwaighofer <aschwaighofer at apple.com>wrote: > Do you have a base run with vectorization turned off? So we could see > where we are degrading things? > I wanted to, but after a few failed attempts, I couldn't pass the option to clang to disable vectorization. I don't want to make Galina reconfig the master every time, so I set up a

Hi, So, I owe you all an apology. I was totally unaware that the llvm.org server, running at UIUC, was still in operation and hosting an active LNT instance. I was under the assumption the LNT server ran elsewhere. As a result, the ability for the LNT bots to submit run information to the "old" LNT server is now gone. I am very sorry for this oversight. In speaking with Chris

As Davide suggests, most likely it's a bot software installation snafu. But the simpler sed script works perfectly, and I'll do that for now. I had understood that LLVM expected people to install GnuWin32, but maybe it's not sufficiently well specified about versions and whatnot. --paulr > -----Original Message----- > From: davide.italiano at gmail.com [mailto:davide.italiano