similar to: GCC toolchain versioning policy? (D43779)

Hmm, i guess i should have mailed cfe-dev too. Doing that now. On Sun, Apr 8, 2018 at 9:38 PM, Roman Lebedev <lebedev.ri at gmail.com> wrote: > Hi. > > As per[1], gcc-4.8 is the oldest supported *major* gcc version. > But what about minor/patch versions? > > When https://reviews.llvm.org/D43779 was initially committed, > a few[2][3] buildbots failed. As i have now

+ Denis and Galina who should know about the affected buildbots and whether it's fine to upgrade them or whether their configurations reflect some important use cases. Sylvestre should know if the release process for LLVM on Ubuntu/Debian relies on the older GCC toolchains somehow. On Mon, Apr 9, 2018 at 1:51 PM Roman Lebedev via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hmm,

On 3 April 2013 14:59, Timur Iskhodzhanov <timurrrr at google.com> wrote: > I'd usually expect tests to work exactly the same way on all platforms. > If there are things that must be handled differently on different > platforms, I'd expect those to have a separate test for each platform > with explicit flags for each of these platforms. > You're absolutely right,

2013/4/3 David Tweed <david.tweed at arm.com>: > Hi, > > As someone working on ARM, we're interested in this sort of issue, to which > there's not yet a complete solution. Some advice below: > > > 2013/4/3 <llvm.buildmaster at lab.llvm.org>: >> The Buildbot has detected a new failure on builder > clang-atom-d2700-ubuntu-rel while building llvm.

Hi Brian, The Atom1-buildbot buildslave has been failing for a few days but I don't think the problem lies in the LLVM/Clang source. From the logs at http://lab.llvm.org:8011/builders/clang-atom-d2700-ubuntu-rel/builds/13632 (and newer builds): ******************** TEST 'Clang :: Driver/x86_features.s' FAILED ******************** Test has no run line!

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:

Why is there a public GN buildbot that sends emails and IRC notifications? That isn't what was agreed upon. Either un-GM it, or silence it. Roman. On Fri, Jun 28, 2019 at 1:05 AM <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: >

Hi LLVM Dev, One of my recent commits has broken build on Ubuntu Atom D2700. 2013/4/3 <llvm.buildmaster at lab.llvm.org>: > The Buildbot has detected a new failure on builder clang-atom-d2700-ubuntu-rel while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/clang-atom-d2700-ubuntu-rel/builds/7852 > > Buildbot URL:

Hello everyone, LLVM buildmasters (both main and staging) will be restarted in 2 hours (~3:00 AM PDT). -- Best Regards, Victor Leschuk | Software Engineer |Access Softek

How do we register buildslaves with the llvm buildbot? We run buildbot internally for clang/llvm. We would like to register our buildslaves with the official llvm buildbot. reed

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

On 8 April 2011 07:58, Duncan Sands <baldrick at free.fr> wrote: > there are several idle ARM buildslaves.  There are the following slaves: Hi Duncan, I could find them on the page http://google1.osuosl.org:8011/buildslaves but I couldn't tell they're ARM. Where do I get this list? Also, I believe they're testing llvm-gcc only (right?). The only target that was testing LLVM

Eric Christopher <echristo at gmail.com> writes: > Nope. If you want it then sooner is always better than later. Ok. > Also keep in mind that some warnings are only enabled with > optimization when building with gcc. Yep. I have a quad-core machine. Can I put two buildslaves on it, each doing a -j2 build? -David

On 04/08/2014 16:20, Dmitri Gribenko wrote: > On Mon, Aug 4, 2014 at 2:20 PM, Dan Liew <dan at su-root.co.uk> wrote: >>>> Second, is there a simple way to test the builder and config before I >>>> commit >>>> it? >>> >>> I am afraid not. >>> >> >> But there is a ugly (and certainly not simple) way to partially test

> 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

Thanks to Jakob's work on Sparcv9 ABI in Clang and recent changes to Sparc code generator, I am happy to announce that Clang can self host itself on Linux/Sparc64 and on FreeBSD/Sparc64. However, it still fails on a few unit tests and nightly tests, primarily due to misaligned memory accesses in the code (See bugs 18482, 18500, 18502, 18536, 18693). Unlike other architectures, misaligned

Hi Reed, > How do we register buildslaves with the llvm buildbot? you point it at lab.llvm.org port 9990 and send the buildslave name and password to Galina. Ciao, Duncan.

2011/10/27 Tanya Lattner <lattner at apple.com>: > Put it in the llvm/docs directory and link to the main documentation page? Maybe add a link the main buildbot page too. I rather suggest; - Put instructions to zorg - Add a link to lab.llvm.org/instruction.html in llvm.org website. llvm/docs might be suitable if llvm-specific issues in buildslaves. ...Takumi >> 7.  Fill the

On Thu, Jun 25, 2020 at 9:59 AM Roman Lebedev <lebedev.ri at gmail.com> wrote: > On Thu, Jun 25, 2020 at 7:48 PM Arthur Eubanks via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > After talking with some NPM people, I believe the ultimate goal after > NPM is enabled by default is to only support `-passes=`, and remove support > for `-foo-pass`. > Hm,

I am unable to connect to build master at:google1.osuosl.org:9990 from my buildslave. See attached twisted9.0.0 log. 2010-02-12 09:50:03-0800 [-] Log opened. 2010-02-12 09:50:03-0800 [-] twistd 9.0.0 (C:\Python26\python.exe 2.6.2) starting up. 2010-02-12 09:50:03-0800 [-] reactor class: twisted.internet.win32eventreactor.Win32Reactor. 2010-02-12 09:50:03-0800 [-] Starting factory