Tim Peters added the comment: FYI, the test fails on my box (32-bit Windows Vista) about 1 time in 3. Here's the latest failure:
AssertionError: 1385160333.612968 not greater than or equal to 1385160333.6129684 And here's another: AssertionError: 1385160530.348423 not greater than or equal to 1385160530.3484235 I can't dig into it more now. Possibilities: 1. The clock isn't always monotonic. 2. MS uses an insane (non-monotonic) rounding algorithm (to move to a 100ns boundary). 3. Python uses an insane (non-monotonic) scheme to convert the time to a float. ---------- nosy: +tim.peters _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19715> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
