Re: [Python-buildbots] Stable builders
On 19/11/2015 3:39 AM, R. David Murray wrote: > It would be nice to have that bot back, since IIRC it was one of the > fastest and so gave quick feedback on bad changesets. If mine are no longer the fastest, I have more work to do :] ___ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
Re: [Python-buildbots] Git installation and roll call
@Zach Ack. git installed (w/ curl http/https support) x 3 FreeBSD buildbot workers -- Regards, Kubilay Kocak > On 8 Dec 2016, at 3:20 PM, Zachary Ware wrote: > > Hi all, > > It has come to my attention that one of our members has been trying to > send mail to the list and it has been silently disappearing. To > determine whether this is a widespread issue, please reply-all to this > message, sending to both the list and me. I'll compare replies I > receive to the archives. If you've also sent messages that were never > replied to, please mention that as well. > > We'll also take this opportunity to ensure that all of our buildslaves > have Git installed in preparation for the GitHub switchover. Please > note whether Git is installed on your slave(s) in your reply. > > Thanks, > -- > Zach > ___ > Python-Buildbots mailing list > Python-Buildbots@python.org > https://mail.python.org/mailman/listinfo/python-buildbots ___ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
Re: [Python-buildbots] FreeBSD 10 buildbot may need a nudge
On 6/25/17 3:54 PM, Nick Coghlan wrote: > It looks like the FreeBSD buildbots had an outage a little while ago, > and the FreeBSD 10 one may need a nudge to get back online (the > FreeBSD Current one looks like it came back automatically). > > Already back: > * http://buildbot.python.org/all/buildslaves/koobs-freebsd-current > > Still offline: > * http://buildbot.python.org/all/buildslaves/koobs-freebsd10 > > Cheers, > Nick. > > P.S. Thanks for providing these Kubilay! They've been invaluable in > attempting to get the PEP 538 locale coercion behaving sensibly on > FreeBSD (and hence hopefully other BSD variants as well). > Vacuum cleaner tripped RCD pulling too much current from the same circuit as heater was running on. Buildbot worker host on same circuit. koobs-freebsd10 worker VM auto restart didn't get through filesystem recovery, which explains its non-return. Should be back in < 10 mins. @Nick fwiw, buildbot (master) does notify buildbot worker admins if and when any workers goes away. I received this: - The Buildbot working for 'Python' has noticed that the buildslave named koobs-freebsd10 went away It last disconnected at Sun Jun 25 05:16:06 2017 (buildmaster-local time) The admin on record (as reported by BUILDSLAVE:info/admin) was 'Kubilay Kocak -- P.S You're more than welcome, and it benefits us as well. CI hosts between upstream projects and downstream consumers (particularly OS's) is one of those rare things that is all upside for everyone involved. ./koobs ___ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
Re: [Python-buildbots] Moving Python.org to Buildbot 9 + Python 3
On 9/22/17 4:12 AM, Zachary Ware wrote: > Hi Craig, > > Sorry I've been largely unresponsive; time has been hard to come by lately. > > On Thu, Sep 21, 2017 at 12:41 PM, Craig Rodrigues > wrote: >> I'm happy to help look into any problems, but you'll have to tell me what >> those >> problems are for me to investigate. > > For starters, there is still a worker connected to the test instance, > which seems to have been failing the daily refleak builds with an > exception since I connected it. However, there's no way to see what > that exception is from the web UI; it looks like it just doesn't load. > I don't think there's anything particularly exotic in the config to > trip it up, so it looks to me like a bug in buildbot (possibly related > to running on Python 3). > > That seems to be a theme with this test instance; pretty much > everything I click on looks incomplete whether logged in or not, and > no errors appear in the logs. Is there something missing/broken in > the configuration? > I can provision a Python 3 buildbot 0.9 worker upon request if that would help ease/verify/test the migration. The FreeBSD buildbot port/package was updated to 0.9 a while ago, and given the lack of backward compatibility (with a 0.8 master), I've had to hold off on upgrades. Getting the 0.9 migration done sooner would for me result in less management and support overhead than keeping it as is, effectively an unsupported state downstream. I would also be happy to switch the existing 2 'stable' FreeBSD (0.8) workers over to 0.9 and a 0.9 server at any time, but would want to ensure that doing so wouldn't: - reduce branch/build-type coverage the 0.8 server config provides - reduce visibility of their statuses to developers. (see them go and stay red) -- Regards, ./koobs ___ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
[Python-buildbots] Re: buildmaster worker naming
Hi Jeremy, Renaming is fine, and we’ve done it previous for our FreeBSD workers. As far as I’m aware the only consequential consideration is that build URLs include(?d) worker names, which were no longer valid after the rename. Newer buildbot may have changed this to use id’s instead, but I haven’t looked for that specifically. > On 29 Mar 2021, at 3:29 am, Jeremy Kloth wrote: > > I'm looking to add another Windows 10 worker to the "buildbot fleet". > Since Win10 updates semi-regularly, is it an issue if the worker name > (BuilderConfig.name) gets changed over the lifetime of the worker? > Currently it would be "Windows10 20H2", but once the next update is > released, the name should be updated to "Windows10 21H1". > > Mostly I'm looking to differentiate the would be two Win10 workers, > but there is a bit of practicality to this as well. Each update (or > version, as it were) does bring changes and features to the base OS, > which can be noticed by test_locale failing > (https://bugs.python.org/issue37945) on recent versions, but not on > the current Windows 10 worker (at version 1803). > > Related to that, if renaming a worker is OK over its lifetime, then > would it be permissible to suffix "1803" to the current Win10 worker > name? > > I'll submit the PR for the new worker once there is clarification. > > Thanks for your time. > > -- > Jeremy Kloth > ___ > Python-Buildbots mailing list -- python-buildbots@python.org > To unsubscribe send an email to python-buildbots-le...@python.org > https://mail.python.org/mailman3/lists/python-buildbots.python.org/ > Member address: koobs.free...@gmail.com ___ Python-Buildbots mailing list -- python-buildbots@python.org To unsubscribe send an email to python-buildbots-le...@python.org https://mail.python.org/mailman3/lists/python-buildbots.python.org/ Member address: arch...@mail-archive.com
[Python-buildbots] Re: buildmaster worker naming
On 29/03/2021 3:29 am, Jeremy Kloth wrote: I'm looking to add another Windows 10 worker to the "buildbot fleet". Since Win10 updates semi-regularly, is it an issue if the worker name (BuilderConfig.name) gets changed over the lifetime of the worker? Currently it would be "Windows10 20H2", but once the next update is released, the name should be updated to "Windows10 21H1". Related to that, if renaming a worker is OK over its lifetime, then would it be permissible to suffix "1803" to the current Win10 worker name? P.S: I'd suggest using a unique random suffix to buildbot worker names (I have 4 char ones for koobs-freebsd-* workers), so that their names are not coupled to versions/branches/upgrades, reducing need for name shuffling down the track. I have this suffix in the worker hostnames so I know what is what. ./koobs ___ Python-Buildbots mailing list -- python-buildbots@python.org To unsubscribe send an email to python-buildbots-le...@python.org https://mail.python.org/mailman3/lists/python-buildbots.python.org/ Member address: arch...@mail-archive.com
