classification
Title: Sporadic test_utime() failures on Solaris
Type: behavior Stage:
Components: Versions:
process
Status: languishing Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Arfrever, christian.heimes, jcea, koobs, larry, pitrou, trent
Priority: low Keywords:

Created on 2012-10-19 13:16 by trent, last changed 2015-04-21 09:51 by koobs.

Messages (3)
msg173339 - (view) Author: Trent Nelson (trent) * (Python committer) Date: 2012-10-19 13:16
This was initially observed in #15745, however, there's a separate problem here.  The current test_utime() on Solaris sporadically (usually) fails along the following lines:

>     self.assertEqual(attr(st0, "st_mtime"), attr(st1, "st_mtime"))
>     AssertionError: 1347752941.275297 != 1347752941.275296

> That is, test_utime() always results in a st1.st_mtime that is
> "off-by-1" from st0.st_mtime.  The precision is well within the
> nanasecond resolution offered by utimensat, so it doesn't appear to be
> the same issue experienced by other platforms.

Run that test in a loop though, and it sometimes passes.  So, there's an underlying bug, somewhere.
msg176978 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2012-12-05 12:36
Doing "./python Lib/test/regrtest.py test_os" for current "default" in Solaris 10 Update 10, I don't see any test failure. I have run it 10.000 times.

I can't reproduce this.

What Solaris 10 version are you using, Trent?
msg201273 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2013-10-25 18:06
Trent, do you still see the failures on Solaris?
History
Date User Action Args
2015-04-21 09:51:44koobssetnosy: + koobs
2013-10-25 18:06:25christian.heimessetstatus: open -> languishing
priority: normal -> low

nosy: + christian.heimes
messages: + msg201273

type: behavior
2012-12-05 12:36:58jceasetmessages: + msg176978
2012-10-19 16:53:57Arfreversetnosy: + Arfrever
2012-10-19 16:32:44jceasetnosy: + jcea
2012-10-19 13:17:38trentsetnosy: + pitrou, larry
2012-10-19 13:16:39trentcreate