similar to: [LLVMdev] llvm-x86_64-linux-checks bot

Hi Cameron, > The llvm-x86_64-linux-checks bot has been out of action for a few days. Does anybody know what's up? It's a pretty useful bot to have, so it would be nice to get it running again. it looks like the machine was rebooted and the buildbot did not automatically start itself on boot (it's supposed to but I don't think it ever worked properly). I've started it by

I’ve had another look, and some of the failing tests don’t use temporary files, so I don’t think this is a case of tests having side-effects. Instead, I’ve noticed that in the build log (http://lab.llvm.org:8011/builders/llvm-clang-x86_64-expensive-checks-win/builds/6552/steps/build-unified-tree/logs/stdio), llvm-tblgen.exe is built (my patch modified it), but the table-generation steps of the

When committing changes on behalf of other contributors, I've started setting the author in Git to be the change author. I think that's better for attribution than just including "Patch By: username" in the message which is default for arc, especially now that we're finally using Git. However, I've noticed that when the change breaks bots, emails are sent only to the

I'm sure it's obvious and I'm just blind, but I can't find the relevant part of that build that's showing a crash. Can you help me out? On Fri, May 8, 2015 at 1:49 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: > +Sergey > > The bot failed on (and looks like it still fails even after LLVM r236877) > on AddressSanitizer-i386-linux ::

Hey Alexey, This bot has been failing for a week, by the looks of it - what's the deal? On Thu, May 7, 2015 at 7:31 PM, <llvm.buildmaster at lab.llvm.org> wrote: > The Buildbot has detected a new failure on builder sanitizer-x86_64-linux > while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/17810 >

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:

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

Happened to me again: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/18273/steps/annotate/logs/stdio In fact, this whole bot has a 20% failure rate with the same failure mode, from looking at the history: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/?numbuilds=50 They all end with this: [100%] Running ThreadSanitizer tests -- Testing: 258 tests, 16 threads --

This bot was failing from http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/29505 until it went green on http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/29534 Anyone happen to know why? I can't quite figure it out from the commits - would be good to know if it's a buildbot issue or a genuine LLVM problem that was in the LLVM code and fixed by one of those

> Please go ahead. We can host the buildbot here: > > http://lab.llvm.org:8011/buildslaves/gribozavr4 Thanks. I guess I'll have to do some reading because I don't have a good high level understanding of how the build bot works. For gribozavr4 does that mean running a new buildbot slave process on the machine or can slaves build multiple configurations (is this the same as what

Hi Tobi, I'm familiar with Zorg, but sometimes people have plans for existing bots I might not be aware of. Are there specific bots for linux/windows I should add this to, or should I leave the existing polly bots alone and create one or two new ones? Of course, Any change would be backward compatible to all other users of the builder. The plan would be have linux and windows cmake

Hello, I've got a couple spare machines I'd like to enlist in build bot. I'm told that the llvm lab folks are the go-to group. I've got a couple machines prepped, I just need to register their names and passwords (I think). Let me know what else I need to do! Thanks, Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 W:

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

On Mon, Apr 22, 2013 at 8:00 AM, Renato Golin <renato.golin at linaro.org>wrote: > Ping? > > This is getting as often as every other run... Is that process downloading > from an internal server? If not, should we? If yes, should we not? > Ok, so we are already downloading from a private server (lab.llvm.org), which IMHO we should be doing because we want tight control over

On 09/29/2015 01:28 PM, David Blaikie via llvm-dev wrote: > The bot has been red and prone to (though not always - as Renato's > pointed out, a red bot that remains red may not send email, but purple > (exception)->red (even if it were red before the exceptional result) > does send email) send email on some of its failures, which adds noise > to the system and makes it

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 folks, I noticed our test-suite bot is failing randomly when getting a timeout on the install phase: http://lab.llvm.org:8011/builders/clang-native-arm-lnt/builds/666/steps/venv.lnt.install/logs/stdio Downloading/unpacking Werkzeug>=0.6.1 (from Flask->LNT==0.4.1dev) Exception: File

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

clean buld forced the regeneration of X86GenGlobalISel.inc & AArch64GenGlobalISel.inc, which may have not happened otherwise. ‫בתאריך יום ו׳, 21 באפר׳ 2017 ב-18:29 מאת ‪Simon Pilgrim via llvm-dev‬‏ <‪ llvm-dev at lists.llvm.org‬‏>:‬ > For reasons I’m not sure about it needs a clean build every so often - > I’ve forced a build at >

Ping? This is getting as often as every other run... Is that process downloading from an internal server? If not, should we? If yes, should we not? thanks, --renato On 20 April 2013 14:03, Renato Golin <renato.golin at linaro.org> wrote: > Hi folks, > > I noticed our test-suite bot is failing randomly when getting a timeout on > the install phase: > > >