<div dir="ltr"><div>Hello Andrzej,</div><div><br></div><div>Please do not update your bots yet. I will explicitly ask later.<br></div><div><br></div><div>Feel free to move other reliably green bots of yours to the production buildbot.</div><div><br></div><div>Thanks</div><div><br></div><div>Galina<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct 9, 2020 at 3:51 AM Andrzej Warzynski <<a href="mailto:andrzej.warzynski@arm.com">andrzej.warzynski@arm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I switched one of our workers to the main Buildbot and everything seems <br>
fine #fingers-crossed. I guess that that was a temporary glitch?<br>
<br>
We haven't updated our local Buildbot installations - still on 0.8.5. <br>
Should we update?<br>
<br>
-Andrzej<br>
<br>
On 09/10/2020 00:44, Galina Kistanova wrote:<br>
> Hi Paula,<br>
> <br>
> This error is fine. The buildbot has tested the worker version. 0.8.x <br>
> apparently does not have that method.<br>
> The error gets handled gracefully on the server side. At least it seems <br>
> so so far.<br>
> <br>
> That should not prevent your bot from connecting.<br>
> <br>
> Thanks<br>
> <br>
> Galina<br>
> <br>
> On Thu, Oct 8, 2020 at 2:11 PM Paula Askar <<a href="mailto:paulatoth@google.com" target="_blank">paulatoth@google.com</a> <br>
> <mailto:<a href="mailto:paulatoth@google.com" target="_blank">paulatoth@google.com</a>>> wrote:<br>
> <br>
> Hey Andrzej,<br>
> <br>
> What are you seeing in your buildbot logs? Is it this error?<br>
> `twisted.spread.flavors.NoSuchMethod: No such method:<br>
> remote_getWorkerInfo`<br>
> <br>
> If so, you might want to try updating your buildbot worker.<br>
> I updated llvmlibc's to 2.8.4 and that seemed to solve the connection<br>
> problem:<br>
> <a href="https://github.com/llvm/llvm-project/commit/f60686f35cc89504f3411f49cf16a651a74be6eb" rel="noreferrer" target="_blank">https://github.com/llvm/llvm-project/commit/f60686f35cc89504f3411f49cf16a651a74be6eb</a><br>
> <br>
> Best,<br>
> Paula Askar<br>
> <br>
> <br>
> On Thu, Oct 8, 2020 at 5:43 AM Andrzej Warzynski via llvm-dev<br>
> <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a> <mailto:<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>> wrote:<br>
> ><br>
> > Our Flang-aarch64 buildbots just won't connect to the main Buildbot<br>
> > master anymore. I switched them to the staging buildbot master<br>
> instead<br>
> > and it seems fine for now. Is there anything that we can/should<br>
> tweak at<br>
> > our end?<br>
> ><br>
> > <a href="http://lab.llvm.org:8014/#/waterfall?tags=flang" rel="noreferrer" target="_blank">http://lab.llvm.org:8014/#/waterfall?tags=flang</a><br>
> ><br>
> > -Andrzej<br>
> ><br>
> > On 08/10/2020 00:31, Galina Kistanova via cfe-dev wrote:<br>
> > > They are online now -<br>
> <a href="http://lab.llvm.org:8011/#/waterfall?tags=sanitizer" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/#/waterfall?tags=sanitizer</a><br>
> > ><br>
> > > AnnotatedCommand has severe design conflict with the new buildbot.<br>
> > > We have changed it to be safe and still do something useful,<br>
> but it will<br>
> > > need more love and care.<br>
> > ><br>
> > > Please let me know if you have some spare time to work on porting<br>
> > > AnnotatedCommand.<br>
> > ><br>
> > > Thanks<br>
> > ><br>
> > > Galina<br>
> > ><br>
> > > On Wed, Oct 7, 2020 at 2:57 PM Vitaly Buka<br>
> <<a href="mailto:vitalybuka@google.com" target="_blank">vitalybuka@google.com</a> <mailto:<a href="mailto:vitalybuka@google.com" target="_blank">vitalybuka@google.com</a>><br>
> > > <mailto:<a href="mailto:vitalybuka@google.com" target="_blank">vitalybuka@google.com</a> <mailto:<a href="mailto:vitalybuka@google.com" target="_blank">vitalybuka@google.com</a>>>><br>
> wrote:<br>
> > ><br>
> > > It looks like all sanitizer builder are still offline<br>
> > > <a href="http://lab.llvm.org:8011/#/builders" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/#/builders</a><br>
> > ><br>
> > > On Tue, 6 Oct 2020 at 00:34, Galina Kistanova via cfe-commits<br>
> > > <<a href="mailto:cfe-commits@lists.llvm.org" target="_blank">cfe-commits@lists.llvm.org</a><br>
> <mailto:<a href="mailto:cfe-commits@lists.llvm.org" target="_blank">cfe-commits@lists.llvm.org</a>><br>
> <mailto:<a href="mailto:cfe-commits@lists.llvm.org" target="_blank">cfe-commits@lists.llvm.org</a><br>
> <mailto:<a href="mailto:cfe-commits@lists.llvm.org" target="_blank">cfe-commits@lists.llvm.org</a>>>> wrote:<br>
> > ><br>
> > > Hello everyone,<br>
> > ><br>
> > > The staging buildbot was up and running for 6 days now, and<br>
> > > looks good.<br>
> > ><br>
> > > Tomorrow at 12:00 PM PDT we will switch the production<br>
> buildbot<br>
> > > to the new version.<br>
> > ><br>
> > > If you are a bot owner, you do not need to do anything<br>
> at this<br>
> > > point, unless I'll ask you to help.<br>
> > > The buildbot will go down for a short period of time,<br>
> and then a<br>
> > > new version will come up and will accept connections<br>
> from your bots.<br>
> > ><br>
> > > Please note that the new version has a bit different URL<br>
> > > structure. You will need to update the bookmarks or<br>
> scripts if<br>
> > > you have stored direct URLs to inside the buldbot.<br>
> > ><br>
> > > We will be watching the production and staging bots and<br>
> will be<br>
> > > improving zorg for the next week or so.<br>
> > ><br>
> > > I will need your feedback about blame e-mails delivery, IRC<br>
> > > reporting issues, and anything you could spot wrong<br>
> with the new<br>
> > > bot. I hope the transition will go smoothly and we<br>
> will handle<br>
> > > issues quickly if any would come up.<br>
> > ><br>
> > > After production is good and we have about a week of<br>
> running<br>
> > > history, I'll ask the bot owners to upgrade buildbots<br>
> on their<br>
> > > side. Please do not upgrade your buildbots unless I'll<br>
> ask you<br>
> > > to. We are trying to limit a number of moving parts at this<br>
> > > stage. We will start accepting change to zorg at this<br>
> point.<br>
> > > Please feel free to talk to me if you will have a special<br>
> > > situation and if you would absolutely have to make changes.<br>
> > ><br>
> > > Thanks for your support and help. And please feel free<br>
> to ask if<br>
> > > you have questions.<br>
> > ><br>
> > > Galina<br>
> > ><br>
> > ><br>
> > > On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova<br>
> > > <<a href="mailto:gkistanova@gmail.com" target="_blank">gkistanova@gmail.com</a> <mailto:<a href="mailto:gkistanova@gmail.com" target="_blank">gkistanova@gmail.com</a>><br>
> <mailto:<a href="mailto:gkistanova@gmail.com" target="_blank">gkistanova@gmail.com</a> <mailto:<a href="mailto:gkistanova@gmail.com" target="_blank">gkistanova@gmail.com</a>>>> wrote:<br>
> > ><br>
> > > Hello everyone,<br>
> > ><br>
> > > The buildbot upgrade is entering the phase when the<br>
> results<br>
> > > to become visible.<br>
> > ><br>
> > > No change is required at this time on any of the<br>
> builders.<br>
> > > The bot owners could upgrade the buildbot on build<br>
> computers<br>
> > > later, at their convenience, as this is not on the<br>
> critical<br>
> > > path.<br>
> > ><br>
> > > We are going to upgrade the staging bot first.<br>
> Then, once<br>
> > > that is stable and all detected issues are<br>
> resolved, we will<br>
> > > upgrade the production bot.<br>
> > ><br>
> > > I will need some help with testing, and will be<br>
> asking to<br>
> > > move some of the builders temporarily to the<br>
> staging. LLVM<br>
> > > buildbot is a piece of critical infrastructure, so<br>
> more eyes<br>
> > > and hands in making sure it works properly the better.<br>
> > ><br>
> > > I'll be posting updates and ETA of particular<br>
> changes in<br>
> > > this thread.<br>
> > ><br>
> > > Please feel free to ask if you have any questions<br>
> or concerns.<br>
> > ><br>
> > > Thanks<br>
> > ><br>
> > > Galina<br>
> > ><br>
> > > _______________________________________________<br>
> > > cfe-commits mailing list<br>
> > > <a href="mailto:cfe-commits@lists.llvm.org" target="_blank">cfe-commits@lists.llvm.org</a> <mailto:<a href="mailto:cfe-commits@lists.llvm.org" target="_blank">cfe-commits@lists.llvm.org</a>><br>
> <mailto:<a href="mailto:cfe-commits@lists.llvm.org" target="_blank">cfe-commits@lists.llvm.org</a> <mailto:<a href="mailto:cfe-commits@lists.llvm.org" target="_blank">cfe-commits@lists.llvm.org</a>>><br>
> > > <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits</a><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > cfe-dev mailing list<br>
> > > <a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a> <mailto:<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>><br>
> > > <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
> > ><br>
> > _______________________________________________<br>
> > LLVM Developers mailing list<br>
> > <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a> <mailto:<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>><br>
> > <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
> <br>
</blockquote></div>