bug report: [ #447945 ] time.time() is not non-decreasing

[Roman Suzi]

On Sat, 4 Aug 2001 zooko at zooko.com wrote:

>
>[[[As an aside on the topic of bug-tracking systems:
>
>   I submitted this on sourceforge, and discovered that it escapes HTML tags so
>   that they just show up in your text.  So this is the worst of both worlds:
>   your formatting options are even more limited than simple ASCII e-mail bug
>   reports would be, and you can't use your familiar e-mail UI, you have to use
>   this slow, unstable, inconvenient, ugly HTML UI.  I suppose the one
>   advantage of an HTML-based bug tracking system like that is that people who
>   can't/won't submit e-mail bug reports might submit HTML bug reports, but
>   I have to suggest that those are often the least valuable bug reports...]]]
>
>
>After spending many hours tracking down weird race conditions in Mojo
>Nation[1], I've finally realized that the problem is that we assumed that
>`time.time()' would return non-decreasing answers. In fact, successive calls to
>`time.time()' can return a *smaller* number than previous calls, as
>demonstrated by this test (Python 2.0 on debian woody):
>
>import time
>
>x = 0
>while 1:
>    ox = x
>    x = time.time()
>    if x < ox:
>        print "this is WRONG: ox: %s, x: %s\n" % (ox, x,)
>    else:
>        print ".",

\me Staring at the dots on the screen

Sorry, I missed your point. Maybe you have some superscalar SMP'uter
which predicts steps to far? ;-)

Sincerely yours, Roman Suzi
-- 
_/ Russia _/ Karelia _/ Petrozavodsk _/ rnd at onego.ru _/
_/ Saturday, August 04, 2001 _/ Powered by Linux RedHat 6.2 _/
_/ "Experience: a name everyone gives to his mistakes." _/