similar to: New buildbot with -Werror

----- Original Message ----- > From: "David Jones via cfe-dev" <cfe-dev at lists.llvm.org> > To: cfe-dev at lists.llvm.org, llvm-dev at lists.llvm.org > Cc: gkistanova at gmail.com > Sent: Tuesday, March 22, 2016 7:00:28 PM > Subject: [cfe-dev] New buildbot with -Werror > > Greetings, > > > I would like to propose adding a buildbot which builds with

On Tue, Mar 22, 2016 at 5:03 PM, David Blaikie <dblaikie at gmail.com> wrote: > Could we change the buildbot config to treat > warnings-as-errors-that-continue in the build step? (so we get the benefit > of further execution tests, while still sending fail-mail, etc for the > warning?) > > That sounds reasonable, although the buildbot implementation seems to be pretty

Could we change the buildbot config to treat warnings-as-errors-that-continue in the build step? (so we get the benefit of further execution tests, while still sending fail-mail, etc for the warning?) On Tue, Mar 22, 2016 at 5:00 PM, David Jones via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Greetings, > > I would like to propose adding a buildbot which builds with -Werror. The

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

I just changed this build on green dragon to warn and email if warnings are found in the console log: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_build/ > On Mar 22, 2016, at 6:24 PM, David Jones via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at

On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think having -Werror bots is a good idea, at least when self hosting. > Non-self-hosting -Werror (i.e. with older versions of Clang, or with GCC, > etc.) might also be useful, but I'm less sure (since we can't fix those > warnings if the warning is the problem). On Tue, Mar

On 06/06/2014 02:33, Alexey Samsonov wrote: > Hi Alp, > > This warning should be fixed by r210301. However, consider > investigating why the frame size appears to be that large. I believe > we build this code with GCC as well and have seen no complaints > from its implementation of -Wframe-larger-than. CC'ing in llvmdev. Like Chandler said it could just be due to lack of

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

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 >

Dmitri Gribenko <gribozavr at gmail.com> writes: > On Tue, Jan 15, 2013 at 2:43 AM, <greened at obbligato.org> wrote: >> The document here explains pretty well how to add a buildslave to the >> buildbot: >> >> http://llvm.org/docs/HowToAddABuilder.html >> >> However, it's not clear to me how to add a new build config. I would >> like

On 5 September 2016 at 23:04, Krzysztof Parzyszek <kparzysz at codeaurora.org> wrote: > Let's first see how bad it is once bots are fixed to build the latest > revision. It's only been a few days and that includes a weekend. Of course. I'll wait until all our bots return from the first round to know the size of the damage. I just wanted to warn all other buildbot owners

Thank you very much for the feedback! What Chandler said about test-suite totally makes sense to me since it's also excluded from LLVM git monorepo. I will try to land benchmark library to LLVM core repo and update it to the latest version. I have not been doing much CMake/project structure before, but I'll start looking into that next week. I'll reach out to Dominic if anything goes

On 6 December 2014 at 00:03, Benjamin Kramer <benny.kra at gmail.com> wrote: > Reverted for now. Not sure what's going on there. Sorry for the breakage. No worries, at least that was easy to spot. Huzzah for buildbots! :) cheers, --renato

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

There is a second issue with the new TableGenBackendSkeleton.cpp file. It is a skeleton file for writing a new TableGen backend. /home/buildbots/docker-RHEL-buildbot/SetupBot/worker_env/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm/llvm/lib/TableGen/TableGenBackendSkeleton.cpp:38:17: error: private field 'Records' is not used [-Werror,-Wunused-private-field] RecordKeeper &Records;

On Tue, Sep 1, 2020 at 3:32 PM David Blaikie <dblaikie at gmail.com> wrote: > On Tue, Sep 1, 2020 at 12:07 PM Nico Weber via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> Hi, >> >> llvmbb's job is to inform people of build breaks. However, it seems to >> trigger for a big list of bots, and at least one of them seems to always be >>

On Tue, 29 Sep 2020 at 18:53, John Paul Adrian Glaubitz < glaubitz at physik.fu-berlin.de> wrote: > So, shall we setup a server for that or is there some existing > infrastructure > from LLVM that is used in this case? > Unfortunately, we don't have a centralised infrastructure like GCC. Each target community is responsible for maintaining their own buildbots. All we

Dmitri Gribenko <gribozavr at gmail.com> writes: > On Tue, Jan 15, 2013 at 7:07 PM, <dag at cray.com> wrote: >> Dmitri Gribenko <gribozavr at gmail.com> writes: >> >>> On Tue, Jan 15, 2013 at 2:43 AM, <greened at obbligato.org> wrote: >>>> The document here explains pretty well how to add a buildslave to the >>>> buildbot:

On Tue, Sep 1, 2020 at 3:57 PM David Blaikie <dblaikie at gmail.com> wrote: > > > On Tue, Sep 1, 2020 at 12:42 PM Nico Weber <thakis at chromium.org> wrote: > >> On Tue, Sep 1, 2020 at 3:32 PM David Blaikie <dblaikie at gmail.com> wrote: >> >>> On Tue, Sep 1, 2020 at 12:07 PM Nico Weber via cfe-dev < >>> cfe-dev at lists.llvm.org>