failures in test_os

[pitrou]

BPO	3580
Nosy	@pitrou, @serhiy-storchaka
Files	fix_test_1565150.patch

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2012-11-22.21:06:46.176>
created_at = <Date 2008-08-17.16:51:44.077>
labels = ['invalid', 'type-bug', 'tests']
title = 'failures in test_os'
updated_at = <Date 2012-11-22.21:06:46.176>
user = 'https://github.com/pitrou'

bugs.python.org fields:

activity = <Date 2012-11-22.21:06:46.176>
actor = 'pitrou'
assignee = 'none'
closed = True
closed_date = <Date 2012-11-22.21:06:46.176>
closer = 'pitrou'
components = ['Tests']
creation = <Date 2008-08-17.16:51:44.077>
creator = 'pitrou'
dependencies = []
files = ['11140']
hgrepos = []
issue_num = 3580
keywords = ['patch']
message_count = 8.0
messages = ['71282', '71287', '71288', '71331', '71333', '71335', '175961', '175971']
nosy_count = 4.0
nosy_names = ['pitrou', 'ocean-city', 'draghuram', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue3580'
versions = ['Python 2.6']

[pitrou]

I get failures under test_os when launched under Windows XP. More
precisely, it's a Windows XP image inside qemu with the Python build dir
in a Samba mount.

======================================================================
FAIL: test_1565150 (main.StatAttributeTests)
----------------------------------------------------------------------

Traceback (most recent call last):
  File "Lib\test\test_os.py", line 291, in test_1565150
    self.assertEquals(os.stat(self.fname).st_mtime, t1)
AssertionError: 1159195039.0 != 1159195039.25

======================================================================
FAIL: test_1686475 (main.StatAttributeTests)
----------------------------------------------------------------------

Traceback (most recent call last):
  File "Lib\test\test_os.py", line 300, in test_1686475
    self.fail("Could not stat pagefile.sys")
AssertionError: Could not stat pagefile.sys

---

[ocean-city]

Maybe will first test failure be fixed by attached patch?
Sorry, this is my bug in bpo-1709599. :-(

[pitrou]

No, it doesn't fix it.
But I've just tried manually, and GetVolumeInformation() returns "NTFS"
for the Samba share. Apparently this is a Samba "feature" to work with
Windows NT. :-)
See http://lists.samba.org/archive/samba/2003-April/065027.html

The other failure is trivial, I've fixed it in r65780.

[draghuram]

The other failure is trivial, I've fixed it in r65780.

bpo-1709112 has been reported earlier in relation to pagefile.sys. Your
patch addresses at least part of the problem there. I wonder if that
issue can be closed.

[pitrou]

According to the aforementioned bug report, we should also add a test
for e.winerror == 5. Chances are that other cases will arise one day or
another...

Since the purpose of the test is, allegedly, to "Verify that an open
file can be stat'ed", it may be simpler to create and open a file
ourselves (test_support.TESTFN being an obvious candidate :-)), and
check that it can be stat'ed. Expecting to be able to access
C:\pagefile.sys sounds as "right" as doing the same with, say,
/etc/passwd under Linux.

(and, incidentally, creating the file ourselves means the test will stop
being Windows-specific)

[draghuram]

On Mon, Aug 18, 2008 at 10:28 AM, Antoine Pitrou <report@bugs.python.org> wrote:

Since the purpose of the test is, allegedly, to "Verify that an open
file can be stat'ed", it may be simpler to create and open a file
ourselves (test_support.TESTFN being an obvious candidate :-)), and

No. Any open file does not do. There has been a discussion on
python-dev some time back about replacing the use of pagefile.sys with
a temporarily created open file. But the problem that spawned this
test case does not occur with just any open file.

[serhiy-storchaka]

Is this reproduced on modern Python versions?

[pitrou]

I don't know. Anyway, it is not really a Python bug, so I suggest we close it.