This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients barry, ned.deily, rhettinger, vstinner
Date 2017-03-27.16:27:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490632042.87.0.811176665087.issue29915@psf.upfronthosting.co.za>
In-reply-to
Content
>The Tiger buildbot fails since many years:
>http://buildbot.python.org/all/builders/x86%20Tiger%203.x/builds/479/steps/test/logs/stdio

That's not true.  The one failing test, test_uuid, was just added last month.  Note that the 3.5 Tiger buildbot has not test failures.

So, one question that perhaps you and Barry can answer is what is the significance of that failure.

>It doesn't seem like anyone take care of this buildbot.

That's also not true.  David Bolen, the owner of the buildbot, is very responsive to requests for updates of third-party libraries on the buildbot.

Getting back to the support of OS X 10.4, to the best of my knowledge we currently do not document anywhere exactly what levels of OS X we support.  We could do that and, yes, we could explicitly drop support for 10.4.  However, at the moment, there just seems to be this one issue which we should understand better before deciding anything.  But, more importantly, at the moment, the 10.4 Tiger buildbot is the *only* working Mac buildbot we have.  Two other Mac buildbots we've had, the "Snow Leopard" and "Yosemite" buildbots have been off-line for many months.  Until we have other working OS X buildbots, the Tiger one should remain.  It is serving a useful purpose.
History
Date User Action Args
2017-03-27 16:27:22ned.deilysetrecipients: + ned.deily, barry, rhettinger, vstinner
2017-03-27 16:27:22ned.deilysetmessageid: <1490632042.87.0.811176665087.issue29915@psf.upfronthosting.co.za>
2017-03-27 16:27:22ned.deilylinkissue29915 messages
2017-03-27 16:27:22ned.deilycreate