[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

STINNER Victor added the comment: I didn't see this race condition recently, I just close the issue. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

STINNER Victor added the comment: Maybe the test can replace shutil.rmtree() with test.support.rmtree() temporarily in test_venv, since test.support.rmtree() handles the anti-malwares protections by retrying and/or sleep (if I recall correctly). --

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

Vinay Sajip added the comment: Not sure what's changed in this area, if anything, to cause this. Can we check if there is anti-virus software running on the buildbot box? This can sometimes hold files open for short periods while scanning for malware, causing this type of permission error

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

Change by Brett Cannon : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

STINNER Victor added the comment: I marked bpo-38983 as a duplicate of this issue. It's the same error in the same function (clear_directory()). Copy of the first message: Failure on AMD64 Windows7 SP1 3.x: https://buildbot.python.org/all/#builders/81/builds/16

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

Jeremy Kloth added the comment: That covers the logging in _force_run(), but the warning.warn() line is also not output, suggesting that the RuntimeWarning is being suppressed somewhere. -- ___ Python tracker

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

STINNER Victor added the comment: > ... is not showing up when the test is re-run in verbose mode. _force_run() logs require verbose >= 2. The test suite is run using: 'Tools\\buildbot\\test.bat' '-x64' '-j2' '-j4' '--timeout' '900' which runs:

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

Jeremy Kloth added the comment: While not getting into the error itself, there seems to be another issue in that the logging that should be happening when the deletion routines from test.support fail:

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

Change by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

STINNER Victor added the comment: Similar error on the same build when the test was re-run in verbose mode: 0:10:55 load avg: 1.82 Re-running test_venv in verbose mode test_deactivate_with_strict_bash_opts (test.test_venv.BasicTest) ... skipped 'not relevant on Windows' test_defaults

[issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\

New submission from STINNER Victor : https://buildbot.python.org/all/#/builders/40/builds/3317 test_executable (test.test_venv.BasicTest) ... ok test_executable_symlinks (test.test_venv.BasicTest) ... skipped 'Needs symlinks' test_isolation (test.test_venv.BasicTest) ... ERROR ERROR