Hello Andrzej, Please do not update your bots yet. I will explicitly ask later.
Feel free to move other reliably green bots of yours to the production buildbot. Thanks Galina On Fri, Oct 9, 2020 at 3:51 AM Andrzej Warzynski <andrzej.warzyn...@arm.com> wrote: > I switched one of our workers to the main Buildbot and everything seems > fine #fingers-crossed. I guess that that was a temporary glitch? > > We haven't updated our local Buildbot installations - still on 0.8.5. > Should we update? > > -Andrzej > > On 09/10/2020 00:44, Galina Kistanova wrote: > > 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 <paulat...@google.com > > <mailto:paulat...@google.com>> wrote: > > > > Hey Andrzej, > > > > What are you seeing in your buildbot logs? Is it this error? > > `twisted.spread.flavors.NoSuchMethod: No such method: > > remote_getWorkerInfo` > > > > If so, you might want to try updating your buildbot worker. > > I updated llvmlibc's to 2.8.4 and that seemed to solve the connection > > problem: > > > https://github.com/llvm/llvm-project/commit/f60686f35cc89504f3411f49cf16a651a74be6eb > > > > Best, > > Paula Askar > > > > > > On Thu, Oct 8, 2020 at 5:43 AM Andrzej Warzynski via llvm-dev > > <llvm-...@lists.llvm.org <mailto:llvm-...@lists.llvm.org>> wrote: > > > > > > 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 - > > 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 know if you have some spare time to work on > porting > > > > AnnotatedCommand. > > > > > > > > Thanks > > > > > > > > Galina > > > > > > > > On Wed, Oct 7, 2020 at 2:57 PM Vitaly Buka > > <vitalyb...@google.com <mailto:vitalyb...@google.com> > > > > <mailto:vitalyb...@google.com <mailto:vitalyb...@google.com>>> > > wrote: > > > > > > > > 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@lists.llvm.org > > <mailto:cfe-commits@lists.llvm.org> > > <mailto:cfe-commits@lists.llvm.org > > <mailto:cfe-commits@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 version. > > > > > > > > If you are a bot owner, you do not need to do anything > > at this > > > > point, unless I'll ask you to help. > > > > The buildbot will go down for a short period of time, > > and then a > > > > new version will come up and will accept connections > > from your bots. > > > > > > > > Please note that the new version has a bit different URL > > > > structure. You will need to update the bookmarks or > > scripts if > > > > you have stored direct URLs to inside the buldbot. > > > > > > > > We will be watching the production and staging bots and > > will be > > > > improving zorg for the next week or so. > > > > > > > > I will need your feedback about blame e-mails delivery, > IRC > > > > reporting issues, and anything you could spot wrong > > with the new > > > > bot. I hope the transition will go smoothly and we > > will handle > > > > issues quickly if any would come up. > > > > > > > > After production is good and we have about a week of > > running > > > > history, I'll ask the bot owners to upgrade buildbots > > on their > > > > side. Please do not upgrade your buildbots unless I'll > > ask you > > > > to. We are trying to limit a number of moving parts at > this > > > > stage. We will start accepting change to zorg at this > > point. > > > > Please feel free to talk to me if you will have a > special > > > > situation and if you would absolutely have to make > changes. > > > > > > > > Thanks for your support and help. And please feel free > > to ask if > > > > you have questions. > > > > > > > > Galina > > > > > > > > > > > > On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova > > > > <gkistan...@gmail.com <mailto:gkistan...@gmail.com> > > <mailto:gkistan...@gmail.com <mailto:gkistan...@gmail.com>>> wrote: > > > > > > > > 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 will > > > > upgrade the production bot. > > > > > > > > I will need some help with testing, and will be > > asking to > > > > move some of the builders temporarily to the > > staging. LLVM > > > > buildbot is a piece of critical infrastructure, so > > more eyes > > > > and hands in making sure it works properly the > better. > > > > > > > > I'll be posting updates and ETA of particular > > changes in > > > > this thread. > > > > > > > > Please feel free to ask if you have any questions > > or concerns. > > > > > > > > Thanks > > > > > > > > Galina > > > > > > > > _______________________________________________ > > > > cfe-commits mailing list > > > > cfe-commits@lists.llvm.org <mailto:cfe-commits@lists.llvm.org> > > <mailto:cfe-commits@lists.llvm.org <mailto: > cfe-commits@lists.llvm.org>> > > > > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits > > > > > > > > > > > > _______________________________________________ > > > > cfe-dev mailing list > > > > cfe-...@lists.llvm.org <mailto:cfe-...@lists.llvm.org> > > > > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev > > > > > > > _______________________________________________ > > > LLVM Developers mailing list > > > llvm-...@lists.llvm.org <mailto:llvm-...@lists.llvm.org> > > > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > >
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
