New submission from Antoine Pitrou <pit...@free.fr>:
test_import fails when run directly after test_coding:
$ ./python -m test test_coding test_import
[1/2] test_coding
[2/2] test_import
test test_import failed -- Traceback (most recent call last):
File "/home/antoine/cpython/default/Lib/test/test_import.py", line 115, in
test_creation_mode
self.assertEqual(stat.S_IMODE(s.st_mode), 0o666 & ~mask)
AssertionError: 436 != 420
384 is 0o600 while 420 is 0o644.
(seen sporadically on some buildbots, e.g.
http://www.python.org/dev/buildbot/all/builders/AMD64%20Snow%20Leopard%202%203.x/builds/1462/steps/test/logs/stdio
)
The same thing happens in 3.2, although the failing test is a different one:
$ ./python -m test test_coding test_import
[1/2] test_coding
[2/2] test_import
test test_import failed -- Traceback (most recent call last):
File "/home/antoine/cpython/32/Lib/test/test_import.py", line 117, in
test_execute_bit_not_copied
stat.S_IRUSR | stat.S_IRGRP | stat.S_IROTH)
AssertionError: 436 != 292
----------
components: Interpreter Core, Tests
messages: 149982
nosy: brett.cannon, ncoghlan, neologix, pitrou
priority: normal
severity: normal
status: open
title: test_import fails after test_coding
type: behavior
versions: Python 3.2, Python 3.3
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13645>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
