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 zach.ware
Recipients Todd.Rovito, amaury.forgeotdarc, ezio.melotti, loewis, python-dev, roger.serwy, terry.reedy, trent, zach.ware
Date 2013-05-10.16:00:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368201643.64.0.626678372455.issue17883@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for your response, Martin.

Martin v. Löwis wrote:
> Zach: Temporarily committing changes to test specific buildbot issues
> is fine

I suppose it would also be beneficial to get some output from the other bots which are *not* failing, to have something to compare with.  In that case, here's a (very) temporary patch we can try for a round of builds.

> asking the slave operator for direct access to the machine 
> may also work.

Trent, what's your policy on letting non-committers play around in your machines? :)  Alternately, do you know of anything about that machine that could be causing the failures?
History
Date User Action Args
2013-05-10 16:00:43zach.waresetrecipients: + zach.ware, loewis, terry.reedy, amaury.forgeotdarc, trent, ezio.melotti, roger.serwy, Todd.Rovito, python-dev
2013-05-10 16:00:43zach.waresetmessageid: <1368201643.64.0.626678372455.issue17883@psf.upfronthosting.co.za>
2013-05-10 16:00:43zach.warelinkissue17883 messages
2013-05-10 16:00:43zach.warecreate