similar to: Silent Build Maser 8014 offline?

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

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

Hey all, It seems that the main buildmaster here is working fine http://lab.llvm.org:8011/ However, I have a 'connection refused' error whilst connecting to the staging buildmaster http://lab.llvm.org:8014/ Are you aware of this Victor and Galina? -------------- next part -------------- An HTML attachment was scrubbed... URL:

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 >

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

Thanks, Galina. It doesn't explain why the test worked on some bots but not this one, but Justin's workaround is okay with me. --paulr From: Galina Kistanova [mailto:gkistanova at gmail.com] Sent: Thursday, November 09, 2017 10:09 AM To: Robinson, Paul Cc: Davide Italiano; llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] Problem with 'sed' on one Windows bot? There is nothing

Hi Asiri, You can use your local master for this or use silent master. Silent buildbot is currently copy of llvm buildbot, but does not sent any notifications. The both have the same set of builders and it's easy to switch a slave between them. To add slave/builder please add your slave and builder to zorg, but point your slave to silent master: use lab.llvm.org:9994 instead of

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

The problem remains after the buildmaster restart. Thanks Galina -----Original Message----- From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Tuesday, December 11, 2012 11:42 AM To: Galina Kistanova Cc: Duncan Sands; llvm-lab-wg at lists.minormatter.com; Galina Kistanova; llvmdev at cs.uiuc.edu Subject: Re: [llvm-lab-wg] FNT testers reporting success even though they failed On Tue,

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

On Tue, Dec 11, 2012 at 11:40 AM, Galina Kistanova <gkistanova at accesssoftek.com> wrote: > Hello everyone, > > It might make sense to start from rebooting the buildmaster, just to make sure everything is all right on this end. > Yesterday I have tried to apply the latest changes from zorg and some of them are broken. > Theoretically, checkconfig shouldn't affect the

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

On 31 October 2016 at 19:46, Galina Kistanova <gkistanova at gmail.com> wrote: > I applied it and reconfigured the master. Thanks Galina! Marco, the build is complaining about Ninja: http://lab.llvm.org:8011/builders/clang-bpf-build/builds/414/steps/cmake%20stage%201/logs/stdio CMake was unable to find a build program corresponding to "Ninja" Now I remember we used ninja by

This issue is back: FNT bots are reporting success in spite of tests failing, and the "report" text is empty again. Did someone change something? Ciao, Duncan. On 12/12/12 07:53, Duncan Sands wrote: > On 11/12/12 23:16, Galina Kistanova wrote: >> The problem remains after the buildmaster restart. > > The FNT builders are now all failing again, and the "report"

Hello everyone, It might make sense to start from rebooting the buildmaster, just to make sure everything is all right on this end. Yesterday I have tried to apply the latest changes from zorg and some of them are broken. Theoretically, checkconfig shouldn't affect the working instance, but the reality could be different... I planned to rollback to the last known-to-be-good revision and

The SVN mirror is back up and running. Please let me know if you would see any issues. Thanks for your patience. On Mon, Mar 13, 2017 at 4:26 PM, Galina Kistanova <gkistanova at gmail.com> wrote: > A quick update. > > The SVN mirror got corrupted by r297634. Svnsync does not like huge > commits. > I'm in the middle of restoring and synch-ing up the mirror. Too soon to

On 11/12/12 23:16, Galina Kistanova wrote: > The problem remains after the buildmaster restart. The FNT builders are now all failing again, and the "report" is no longer empty. Does anyone know what fixed them? Ciao, Duncan. > > Thanks > > Galina > > > > -----Original Message----- > From: David Blaikie [mailto:dblaikie at gmail.com] > Sent: Tuesday,

I was hoping to avoid the trouble of having to setup a master buildbot. But may be it's just easier to run Zorg as-is locally alongside the buildslave. I'll give that a go. Cheers, / Asiri On Fri, May 27, 2016 at 8:45 PM, Yaron Keren <yaron.keren at gmail.com> wrote: > You don't really need to use the llvm builders infrastructure, just setup > a local jenkins (or

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 *