[issue23774] Test failures when unable to write to install location

Change by Irit Katriel : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> allow the testsuite to run in the installed location ___ Python tracker ___

[issue23774] Test failures when unable to write to install location

Berker Peksag added the comment: > test_compileall See issue 21264 I think this can be closed as a duplicate of issue 17750. -- nosy: +berker.peksag ___ Python tracker ___

[issue23774] Test failures when unable to write to install location

R. David Murray added the comment: We need a buildbot that runs tests on an installed python. The general problem is not windows-only. -- nosy: +r.david.murray ___ Python tracker _

[issue23774] Test failures when unable to write to install location

Serhiy Storchaka added the comment: There is a guard for zipfile tests (requiresWriteAccess). The question is why it doesn't work for this test but works for other tests. -- nosy: +serhiy.storchaka ___ Python tracker

[issue23774] Test failures when unable to write to install location

New submission from Steve Dower: The following tests fail when run in an all-users installation because they cannot write to the install directory: test_compileall test_tcl test_tools test_zipfile See the attached file for traces. >From Ned Deily: Regarding tests trying to write into the inst