See
https://mail.python.org/archives/list/python-...@python.org/message/SKMYKKM3ZON3IW75P5VNXI34BYE4X323/
.
There was some maintenance and cleaning up done for the buildbot database,
it looks like several of the numbers were changed around.
On Thu, Nov 28, 2019 at 2:36 PM Michael wrote:
> https
> AMD64 FreeBSD Shared 3.8 never ran successfully but is listed as stable.
I believe that one has previously ran successfully, but not since the reset
that was recently performed on the buildbot database on November 28th. See
https://mail.python.org/archives/list/python-...@python.org/message/SKM
The following buildbots have been consistently failing across unrelated
commits in cpython's master branch, during their compilation stages: "AMD64
Windows7 SP1 3.x" (https://buildbot.python.org/all/#/builders/81) and "x86
Windows7 3.x" (https://buildbot.python.org/all/#/builders/150). Based on
the
on 3.9+ no longer needs to support Windows 7 given its
> release will be after the Windows 7 EOL. The builder removal just hasn't
> happened yet.
>
> -- David
>
> On Sat, Feb 8, 2020 at 12:52 AM Kyle Stanley wrote:
>
>> The following buildbots have been consistent
Victor Stinner wrote:
> Regular buildbot jobs triggered on commits into the 2.7 are still
> enabled, but there is no more commit in this branch :-)
Are all of the the buildbot jobs for the 2.7 branch going to be entirely
disabled after the final release (2.7.18) planned for mid-April?
On Mon, F
> What needs to be fixed here? I have some time and some experience.
IIUC, it's a matter of the buildbot infrastructure team obtaining the funds
and upgrading the disk space for the buildbot server rather than something
that can be fixed by anyone.
On Fri, Mar 13, 2020 at 5:31 PM Matt Billenstei
