similar to: mips builders on LLVM buildbot?

Hi Galina, I will try to find owners of these buildbots. I hope to get results on the next week. On Sat, Nov 3, 2018 at 1:48 AM Daniel Sanders <daniel_l_sanders at apple.com> wrote: > > Hi Galina, > > I'm sad that they appear to have been abandoned but no objections from me as I'm not the admin for any of these anymore. A couple of them were taken over by a colleague

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

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 >

Galina, Looks like the build bots have frozen. Expected? Joe Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 jabbey at arxan.com<mailto:jabbey at arxan.com> www.arxan.com<http://www.arxan.com/> On Nov 18, 2011, at 11:49 AM, Galina Kistanova wrote: Author: gkistanova Date: Fri Nov 18 13:49:26 2011 New Revision: 144978

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 -

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

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 Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via lldb-commits < lldb-commits at lists.llvm.org> wrote: > They are online now - http://lab.llvm.org:8011/#/waterfall?tags=sanitizer > > AnnotatedCommand has severe design conflict with the new buildbot. > We have changed it to be safe and still do something useful, but it will > need more love and care. > > Please let me

Thank you. Alexei just committed the change to SVN. Regards, Marco Leogrande Sent by a carbon-based life form; hence, it may contain repetitions, inaccuracies, logical fallacies and repetitions. On Wed, Jun 17, 2015 at 2:52 PM, Galina Kistanova <gkistanova at gmail.com> wrote: > LGTM. > Please commit. > > Thanks > > Galina > > On Tue, Jun 16, 2015 at 8:32 PM,

I'd like to take code ownership of the LLVM Buildbot code. Thanks Galina

Switched all but PPC, I don't have access to them. But they run the same script as sanitizer-x86_64-linux. http://lab.llvm.org:8014/#/waterfall?tags=sanitizer On Mon, 12 Oct 2020 at 19:19, Galina Kistanova <gkistanova at gmail.com> wrote: > We have a better version of AnnotatedCommand on the staging. It should be > a functional equivalent of the old one. > We need to stress

Hello everyone, LLVM buildmaster is back to work. Two slaves remain off for now as they produce a lot of warnings and their log files are way too big. The next builds have full logs available. Hope this helps to fix this issue: http://lab.llvm.org:8011/builders/clang-x86-windows-msvc2015/builds/8716 http://lab.llvm.org:8011/builders/clang-with-thin-lto-windows/builds/2645 Thanks Galina

That would explain it. The commit messages were quite long (especially the second one) and a commit with a smaller message has shown up. Thanks for letting me know. I'll try to keep them a bit more reasonable in future. > -----Original Message----- > From: NAKAMURA Takumi [mailto:geek4civic at gmail.com] > Sent: 15 November 2013 16:28 > To: Daniel Sanders > Cc: LLVM Developers

Galina, thanks again for your help. I have cooked a new patch that should make a bit more sense. I have added the new builder under _get_experimental_scheduled_builders(), as the comment above that function suggested me it would be a good idea. :) Does it look a reasonable start? Regards, Marco Leogrande Sent by a carbon-based life form; hence, it may contain repetitions, inaccuracies,

Hello everyone, The builder http://lab.llvm.org:8011/builders/lld-x86_64-win7​ is up and running. It builds lld and runs lld tests for each commit. The build shows 11 warnings, everything else is green. Do you think it is feasible to treat warnings as errors, or better keep it this way for now? Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL:

Ah, ...no. please don't hesitate to write logs ;) It must be the subject in the buildbot, not in developer guys. Galina, I'll write up later, how to tweak this issue. It is not resolved in released versions, though. The easiest way is to tweak svnpoller. 2013/11/16 Daniel Sanders <Daniel.Sanders at imgtec.com>: > That would explain it. The commit messages were quite long

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:

Dmitri Gribenko <gribozavr at gmail.com> writes: >> Right, I get that. Actually I would probably use --enable-werror. >> >> Should I create a patch for builders.py to add a new config? > > Yes. Send it to llvm-commits and CC Galina Kistanova. Ok, cool. Thanks! >> Is there a way to map a config so that it only even builds on a certain >> buildslave?

Hi Galina, The failing build was http://lab.llvm.org:8011/builders/clang-cmake-mips/builds/10220 and the commit that caused it was 'r251331 [compiler-rt] Fix ptrace interceptor for aarch64'. ________________________________ From: Galina Kistanova [gkistanova at gmail.com] Sent: 02 November 2015 16:03 To: Daniel Sanders Cc: Renato Golin; Bill Seurer; LLVM Dev Subject: Re: [llvm-dev]

Hello everyone, We have a number of issues with the current buildbot infrastructure. During this week I will be addressing 2 which I think are most important. 1. There is no well specified dependencies, so all builders get triggered by any change in any of watched projects. I.e. lldb change triggers clang build and versa versa. 2. If a project depends on multiple others, sequential changes could