[issue11956] 3.3 : test_import.py causes 'make test' to fail

Changes by Charles-François Natali : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Roundup Robot added the comment: New changeset cbda512c6d7f by Charles-François Natali in branch '3.2': Issue #11956: Always skip test_import.test_unwritable_directory when run as http://hg.python.org/cpython/rev/cbda512c6d7f New changeset 971093a75613 by Charles-François Natali in branch 'defa

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Roundup Robot added the comment: New changeset 7697223df6df by Charles-François Natali in branch '3.2': Issue #11956: Skip test_import.test_unwritable_directory on FreeBSD when run as http://hg.python.org/cpython/rev/7697223df6df New changeset 58870fe9a604 by Charles-François Natali in branch '

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Éric Araujo added the comment: Disregard my remark; David in msg134804 expressed support for this, and given that there are Python programs run as root for sysadmin tasks, it makes sense to make sure the code is tested when run by root. -- ___ Pyth

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Éric Araujo added the comment: It seems strange to build and test Python as root. -- nosy: +eric.araujo ___ Python tracker ___ ___ Py

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Changes by Brian Curtin : -- components: +Tests -Build type: crash -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Jason Vas Dias added the comment: Aha ! Yes, the test DOES succeed as a non-root user , and yes, if you are super user you can override any write bits in directory permissions if you own the directory. So the fix ? : skip 'unwritable_directory' test if you are root - here's the patch -

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Jason Vas Dias added the comment: oops, no sorry it was this bit from the strace log : umask(0222) = 022 stat("./@test_9634_tmp", 0x7fff7ef64130) = -1 ENOENT (No such file or directory) open("./@test_9634_tmp.cpython-33m.so", O_RDONLY) = -1 ENOENT (No such file or d

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Jason Vas Dias added the comment: So, in the statement that fails : self.assertFalse(os.path.exists(os.path.join(...))) . either self.assertFalse is failing or os.path.exists is failing or os.path.join is failing. The fact that the error message is 'AssertionError: True is not false' suggest

[issue11956] 3.3 : test_import.py causes 'make test' to fail

Changes by Jason Vas Dias : -- components: +Build type: -> crash versions: +Python 3.3 ___ Python tracker ___ ___ Python-bugs-list ma

[issue11956] 3.3 : test_import.py causes 'make test' to fail

New submission from Jason Vas Dias : Hi - I've been experiencing many errors trying to build any version of Python that will pass its test suite - see issues : #11946 , #11954 - and now I've been advised to raise bugs about each test failure - hence this bug. For details of my config and build pr