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 r.david.murray
Recipients belopolsky, larry, r.david.murray, serhiy.storchaka, terry.reedy
Date 2015-05-19.12:20:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432038036.63.0.924111687033.issue24215@psf.upfronthosting.co.za>
In-reply-to
Content
I've backed out the change set that broke the buildbots (see de9c43fabda6).

I can understand this changeset getting committed, since one doesn't normally expect a change in the tests to break other tests (though I myself do often run the full test suite anyway), but it is not acceptable that the breakage of the buildbots was not addressed quickly.  The problem should have been fixed or the changeset backed out within hours of the problem being recognized.
History
Date User Action Args
2015-05-19 12:20:36r.david.murraysetrecipients: + r.david.murray, terry.reedy, belopolsky, larry, serhiy.storchaka
2015-05-19 12:20:36r.david.murraysetmessageid: <1432038036.63.0.924111687033.issue24215@psf.upfronthosting.co.za>
2015-05-19 12:20:36r.david.murraylinkissue24215 messages
2015-05-19 12:20:36r.david.murraycreate