builder
for that configuration (VC9 only) if that is something we are
interested in doing.
Thanks
--
Jeremy Kloth
___
Python-Buildbots mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-buildbots
I'm in the process of moving, so my buildslave is going to be down for
at least 1 week (maybe a little longer).
Hopefully the GitHub migration issues wrt Windows will be shaken out by then...
Sorry for any inconvenience that this may bring.
Thanks
--
Jeremy
e the availability of the workers (especially the slower ones).
Ideally, this could be implemented server-side so as to eliminate
"false" successes. I would think that this would help those watching
the buildbots (Victor!) for erroneous commits.
-
rg/all/#/builders/130/builds/30
http://buildbot.python.org/all/#/builders/130/builds/29
http://buildbot.python.org/all/#/builders/40/builds/414
http://buildbot.python.org/all/#/builders/17/builds/116
--
Jeremy Kloth
___
Python-Buildbots mailing list
Python-Bui
On Sat, Jun 9, 2018 at 11:56 AM Zachary Ware
wrote:
> Good point. I've expanded the definition of an unimportant file, see
> https://github.com/python/buildmaster-config/pull/38/files which is
> now deployed.
Thanks, that should eliminate most all false builds.
--
:
commit: ab54b9a130c88f708077c2ef6c4963b632c132b3
branch: master
author: Emmanuel Arias
committer: Terry Jan Reedy
date: 2019-01-03T02:47:58-05:00
--
Jeremy Kloth
___
Python-Buildbots mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-buildbots
It seems that the buildbot master has been updated and lost all the
previous build information.
Also, the workers have been renumbered so previous links (e.g., in the
BPO reports) are now broken.
--
Jeremy Kloth
___
Python-Buildbots mailing list
ut a notification to python-dev about this
change. Anyone who watches the buildbots regularly may be in for a
bit of a shock when they do not see any status for recent builds. Or,
like me, who have a particular worker bookmarked (i.e., my buildbot)
and suddenly it points to a completely
I'm in the process of moving, so my buildslave is going to be down for
at least 1 week (maybe a little longer).
Sorry for any inconvenience that this may bring.
Thanks
--
Jeremy Kloth
___
Python-Buildbots mailing list -- [email protected]
'll submit the PR for the new worker once there is clarification.
Thanks for your time.
--
Jeremy Kloth
___
Python-Buildbots mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mai
> > On Sun, Mar 28, 2021 at 12:29 PM Jeremy Kloth
> > wrote:
> > > Mostly I'm looking to differentiate the would be two Win10 workers
> > From: "David Bolen"
> > Personally, I'd prefer not to encode additional release details in the
>
nce the PR is merged, the worker is ready to go, I just need to start
the service (the build master will use my existing password).
--
Jeremy Kloth
___
Python-Buildbots mailing list -- [email protected]
To unsubscribe send an email to python-bu
> Note that the failed test is test_winconsoleio. I'm assuming
> something changed in this release of Windows meaning getting this
> worker going will help track that down :)
I've created an issue for tracking the test_winconsoleio error:
https://bugs.python.org/issue4535
On Sun, Oct 3, 2021 at 8:46 AM Jeremy Kloth wrote:
> I've created an issue for tracking the test_winconsoleio error:
>
> https://bugs.python.org/issue45354
PR submitted to fix the apparently more strict handling of device naming.
--
overage as David also has workers
for these areas.
Thanks.
--
Jeremy Kloth
___
Python-Buildbots mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/li
15 matches
Mail list logo
