----- Original Message -----
> From: "David Bolen" <db3l....@gmail.com>
> To: "Jeremy Kloth" <jeremy.kl...@gmail.com>
> Cc: "python-buildbots" <Python-Buildbots@python.org>
> Sent: Monday, March 29, 2021 4:29:29 AM
> Subject: [Python-buildbots] Re: buildmaster worker naming
>
> With respect to the current Win10 worker, the older system status looks
> like my fault - it appears stuck waiting for a manual reboot for prior
> updates (I guess at some point it stopped doing it automatically), so I'll
> get that caught up.
>
> Personally, I'd prefer not to encode additional release details in the
> worker name itself, leaving that stable, but it is a detail that could be
> included in the worker info field, so I'll get that adjusted too.
>
> -- David
>
>
> On Sun, Mar 28, 2021 at 12:29 PM Jeremy Kloth <jeremy.kl...@gmail.com>
> 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: db3l....@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: cstra...@redhat.com
>
>
I'm doing the same thing. For example I have a cstratak-RHEL7-ppc64le named
worker which indicated the architecture and the OS major version, however the
minor version (7.9) is noted at the host's description. Whenever I'd update
(e.g. from 7.8 to 7.9) I'd just change the description.
--
Regards,
Charalampos Stratakis
Software Engineer
Python Maintenance Team, Red Hat
_______________________________________________
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
