similar to: [LLVMdev] Code Ownership - Buildbot

On Thu, Nov 15, 2012 at 2:10 PM, Sean Silva <silvas at purdue.edu> wrote: > kinda random, but do we have a centralized list of all of the > buildbots? I see a lot of different URL's in IRC, but no list so I can > check "all of the waterfalls". I'm not talking about the specific bots > (e.g. llvm-x86_64-ubuntu) but the "fleets"

kinda random, but do we have a centralized list of all of the buildbots? I see a lot of different URL's in IRC, but no list so I can check "all of the waterfalls". I'm not talking about the specific bots (e.g. llvm-x86_64-ubuntu) but the "fleets" (e.g.http://lab.llvm.org). Could you maybe add a little bulleted list (or link to a list) to docs/HowToAddABuilder.rst?

On 15.11.2012, at 23:16, David Blaikie <dblaikie at gmail.com> wrote: > On Thu, Nov 15, 2012 at 2:10 PM, Sean Silva <silvas at purdue.edu> wrote: >> kinda random, but do we have a centralized list of all of the >> buildbots? I see a lot of different URL's in IRC, but no list so I can >> check "all of the waterfalls". I'm not talking about the

Here is a trivial reason why I have not propagated http://bb.pgr.jp/ . Sometimes (but I suppose rarely) he reports false alarm in a few points. He'd send blames to the llvm-testresults if his master (aka I) knew he were mature. I don't also want him promoted and called as one of official buildbots. He is my pet, though, I expect he should be helpful to the developers. ...Takumi

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,

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 Marco, Welcome aboard! slaves.py keeps the build slaves definitions, builders.py keeps the builders definitions. You have to have both. The steps of adding a new slave is here: http://llvm.org/docs/HowToAddABuilder.html. Please make sure you done the step # 10 before bringing your slave up, otherwise it wouldn't be authorized by the master and will be blacklisted after multiple

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 >

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 -

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

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

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

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

Hi All, Recent conversations [1][2] would suggest we need to rethink zorg or at the very least improve the documentation. I've CC'ed Daniel Dunbar, Galina Kistanova and Duncan Sands because it seemed that they have contributed the most code to Zorg Organisation ========= The current organisation of the Zorg repository doesn't make a huge amount of sense from my perspective. There

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

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

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

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

Hello, I am going to take LLVM build master down for maintenance tonight. Sorry for inconvenience. If this time is not OK for anyone speak please! Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130111/b02e9e8e/attachment.html>