[issue17064] Fix sporadic buildbot failures for test_mailbox

2013-02-11 Thread Roundup Robot
Roundup Robot added the comment: New changeset bbeff2958cc5 by R David Murray in branch '3.2': #17064: fix sporadic permission errors in test_mailbox on windows. http://hg.python.org/cpython/rev/bbeff2958cc5 New changeset 3e3915cbfde3 by R David Murray in branch '3.3': Merge: #17064: fix sporadi

[issue17064] Fix sporadic buildbot failures for test_mailbox

2013-02-11 Thread R. David Murray
R. David Murray added the comment: Thanks, Jeremy. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> behavior versions: +Python 2.7, Python 3.2 -Python 3.5 ___ Python tracker _

[issue17064] Fix sporadic buildbot failures for test_mailbox

2013-01-28 Thread R. David Murray
R. David Murray added the comment: Ah, excellent. I had missed that change. This looks good then. Hopefully it will work :) -- ___ Python tracker ___ _

[issue17064] Fix sporadic buildbot failures for test_mailbox

2013-01-28 Thread Jeremy Kloth
Jeremy Kloth added the comment: Actually, the support functions (as of 3.3) attempt to work around the access errors. They attempt to wait (to a point) for a successful operation before returning to the caller. See issue15496 for details. It is usually the case that the previous operation ha

[issue17064] Fix sporadic buildbot failures for test_mailbox

2013-01-28 Thread R. David Murray
R. David Murray added the comment: I think the support functions just ignore errors. Isn't this going to continue to leave garbage on the buildbot filesystem without fixing the underlying problem? I wonder if this is a variation on the usual Windows access errors, in which case perhaps that

[issue17064] Fix sporadic buildbot failures for test_mailbox

2013-01-28 Thread Jeremy Kloth
New submission from Jeremy Kloth: Attached is an attempt at fixing the sporadic failures of test_mailbox on the AMD64 Windows buildbot. It fails due to access errors on some directories which leads me to believe the helper functions in test.support should fix the problem. -- component