similar to: No mac bots on http://lab.llvm.org:8011/console ?

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

Why does GN bot still send mails? I thought it got fixed? On Wed, Jul 3, 2019 at 1:44 PM <llvm.buildmaster at lab.llvm.org> wrote: > > The Buildbot has detected a new failure on builder sanitizer-x86_64-linux-gn while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-gn/builds/1820 > > Buildbot URL:

I'm working on lldb. I've just submitted a very small change (r217229) to Triple.h/.cpp. Soon after I get a mail subject: buildbot failure in LLVM on lld-x86_64-darwin13 Details: http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571 Blamelist: mg11 My small change certainly did not cause lldb's build to fail on my machine. I looked into the build-log:

Hi Fred, Thanks. How did you get to " The build log show this error: /Users/buildslave/as-bldslv9/lld-x86_64-darwin13/llvm.src/lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp:92:11: error: enumeration values 'KalimbaSubArch_v3', 'KalimbaSubArch_v4', and 'KalimbaSubArch_v5' not handled in switch [-Werror,-Wswitch] switch (triple.getSubArch()) { " from here

vitalybuka, sanitizer-x86_64-linux-gn is _still_ on http://lab.llvm.org:8011/console . Can we please get it removed? On Wed, Jul 3, 2019 at 7:07 AM Nico Weber <thakis at chromium.org> wrote: > https://reviews.llvm.org/D63909 landed. Maybe it needs a master restart > to have an effect? > > On Wed, Jul 3, 2019 at 1:03 PM Roman Lebedev <lebedev.ri at gmail.com> wrote: >

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

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 *

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

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:

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

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

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

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

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

+llvm-dev On Mon, Jan 14, 2019 at 1:46 PM David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 14/01/2019 10:36, Ilya Biryukov via llvm-dev wrote: > > To reiterate, our proposal was to create a repository for each of the > > LLVM subprojects under the official LLVM GitHub account, e.g. > > github.com/llvm/clangd <http://github.com/llvm/clangd>. > >

On 5 September 2016 at 22:12, Renato Golin <renato.golin at linaro.org> wrote: > Should we revert this? This is pretty serious? Can we fix this quickly > on the bots? Just FYI, I'm moving the "llvm" directory away and making it as a symlink to "llvm.src", at least until we sort out this problem. Since this has been going on from Sep 1st, I believe we'll