New submission from Trent Nelson: 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. ---------- messages: 173339 nosy: trent priority: normal severity: normal status: open title: Sporadic test_utime() failures on Solaris _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16287> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
