[issue17750] allow the testsuite to run in the installed location

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17750] allow the testsuite to run in the installed location

Changes by Serhiy Storchaka : -- dependencies: +test_compileall fails when run by unprivileged user on installed Python, test_zipfile failure when run by unprivileged user with installed Python ___ Python tracker

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose : -- dependencies: +test_code_module tests fail when run from the installed location ___ Python tracker ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test failure introduced by the fix for issue #22462 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Mark Lawrence added the comment: How do we stand with eight outstanding issues here? -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_compileall fails to build in the installed location ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_zipfile fails to run in the installed location ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_pydoc fails with the installed testsuite (2.7) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

New submission from Matthias Klose: [Meta issue, opening separate issues for test cases] The default install always installs the testsuite together with all the python batteries. So make sure that you can run the testsuite can run from the installed location too. - some tests require the

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_shutil.TestWhich.test_non_matching_mode fails when running as root ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- nosy: +jibel ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___ ___ Python-bugs-list mailing

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +ctypes/test/test_macholib.py fails when run from the installed location ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +many distutils tests fail when run from the installed location ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_zipfile: requires write access to test and email.test ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_ctypes assumes LANG=C LC_ALL=C ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_builtin assumes LANG=C ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_syntax_error fails when run in the installed location ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_executable_without_cwd fails when run in the installed location ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___ ___ Python-bugs-list mailing

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_site fails when the user does not have a home directory ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

R. David Murray added the comment: This has been fixed and broken again several times in the past[1]. We need a buildbot that runs the tests installed[2]. Antoine, do you have any thoughts about how to set up such a thing? I'm willing to host it. [1] I believe there used to be a program

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_pydoc fails with the installed testsuite ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

Ned Deily added the comment: We could change an existing buildbot, say one of the snakebite buildbots, to add a `make install` and run the tests from it. I don't think it should be very difficult. Just make sure ./configure --prefix= has a reasonable value like a dedicated directory (rather

[issue17750] allow the testsuite to run in the installed location

R. David Murray added the comment: It occurs to me that the tricky bit is that the install directory contents should be (a) read-only (easy) and ideally (b) owned by root (a little trickier, but doable with a setuid script or tailored sudo command). --

[issue17750] allow the testsuite to run in the installed location

Changes by Matthias Klose d...@debian.org: -- dependencies: +test_subprocess test_executable_without_cwd fails when run with installed python ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750

[issue17750] allow the testsuite to run in the installed location

Matthias Klose added the comment: it doesn't have to be root, just another user as for running the testsuite. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17750 ___

[issue17750] allow the testsuite to run in the installed location

R. David Murray added the comment: Right, it doesn't *have* to be root, but that would be the typical situation when the tests are run with Python installed. Having it be any other user still requires some privilege increase. -- ___ Python tracker