On 5/15/06, Tim Peters <tim.peters at gmail.com> wrote: > > [Tim] > > "Something went wrong" here on Windows. The Windows buildbot slaves > > other than mine eventually died with: > > > > """ > > ... > > test_tarfile > > > > command timed out: 1200 seconds without output > > """: > > > > I was working on my box at the time, and it became dramatically > > unusable: took about two minutes just to swap enough of the OS back > > in to _bring up_ Task Manager to see what was going on. ... > > OK, I fixed that, but unfortunately the checkin comment was correct: > > The Windows buildbot slaves shouldn't swap themselves to death > anymore. However, test_tarfile may still fail because of a > temp directory left behind from a previous failing run. > Windows buildbot owners may need to remove that directory > by hand. > > I did that on my box, and test_tarfile passes there now, but > test_tarfile is still failing on other Windows slaves; e.g., > > > http://www.python.org/dev/buildbot/all/x86%20W2k%20trunk/builds/694/step-test/0 > > ... > > WindowsError: [Error 183] Cannot create a file when that file already > exists: > 'c:\\docume~1\\trentm~1.act\\locals~1\\temp\\testtar.dir\\directory' > _______________________________________________ > > Ignorant question probably, but why can't the test just check for the directory first, and remove it if it exists? -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060515/ba266eba/attachment.htm
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4