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 ncoghlan
Recipients georg.brandl, ncoghlan
Date 2012-08-01.13:30:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343827804.07.0.425515249327.issue15526@psf.upfronthosting.co.za>
In-reply-to
Content
regrtest bailed out completely on one of the Windows 7 builders due to a problem with accessing the temporary working directory:

http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/410/steps/test/logs/stdio

It's seems a touch suspicious that test_fork1 just so happened to be the test executed right before test_startfile blew up.

Not marking as a blocker yet, since my initial assumption is that it's a race condition with a particular sequence of tests rather than a problem in Python itself. I'll change my mind if it happens again on the rebuild I just forced.
History
Date User Action Args
2012-08-01 13:30:04ncoghlansetrecipients: + ncoghlan, georg.brandl
2012-08-01 13:30:04ncoghlansetmessageid: <1343827804.07.0.425515249327.issue15526@psf.upfronthosting.co.za>
2012-08-01 13:30:03ncoghlanlinkissue15526 messages
2012-08-01 13:30:02ncoghlancreate