Vitaly Buka via llvm-dev
2020-Oct-07 21:57 UTC
[llvm-dev] Upcoming upgrade of LLVM buildbot
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 > 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 <gkistanova at 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 at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201007/60ff1e4c/attachment.html>
Galina Kistanova via llvm-dev
2020-Oct-07 23:31 UTC
[llvm-dev] Upcoming upgrade of LLVM buildbot
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 <vitalybuka at 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 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 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 <gkistanova at 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 at lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201007/5674a63a/attachment.html>
Andrzej Warzynski via llvm-dev
2020-Oct-08 09:43 UTC
[llvm-dev] [cfe-dev] Upcoming upgrade of LLVM buildbot
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 <vitalybuka at google.com > <mailto:vitalybuka at 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 at lists.llvm.org <mailto: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 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 > <gkistanova at gmail.com <mailto:gkistanova at 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 at lists.llvm.org <mailto:cfe-commits at lists.llvm.org> > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits > > > _______________________________________________ > cfe-dev mailing list > cfe-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev >
Vitaly Buka via llvm-dev
2020-Oct-12 10:33 UTC
[llvm-dev] Upcoming upgrade of LLVM buildbot
Thanks, I see them. On Wed, 7 Oct 2020 at 16:32, Galina Kistanova <gkistanova at gmail.com> 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. > > It's unlikely in near future.What is missing exactly?> Thanks > > Galina > > On Wed, Oct 7, 2020 at 2:57 PM Vitaly Buka <vitalybuka at 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 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 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 <gkistanova at 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 at lists.llvm.org >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits >>> >>-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201012/027055f3/attachment.html>
Reid Kleckner via llvm-dev
2020-Oct-12 18:39 UTC
[llvm-dev] [Lldb-commits] Upcoming upgrade of LLVM buildbot
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 know if you have some spare time to work on porting > AnnotatedCommand. >That's unfortunate, it would've been good to know that earlier. I and another team member have spent a fair amount of time porting things to use more AnnotatedCommand steps, because it gives us the flexibility to test steps locally and make changes to the steps without restarting the buildbot master. IMO that is the Right Way to define steps: a script that you can run locally on a machine that satisfies the OS and dep requirements of the script. I am restarting the two bots that I am responsible for, and may need some help debugging further issues soon. I'll let you know. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201012/c3f4f389/attachment.html>