> Exactly how does it fail?
[Raymond Hettinger, on bug737473]
> Traceback (most recent call last):
> File "test_traceback.py", line 79, in test_bug737473
> test_bug737473.test()
> File "c:\windows\temp\tmpsj7w5a\test_bug737473.py", line 2, in test
> ValueError
That helps.
>> Does it work if you force the test to take the time.sleep()
>> path instead of the os.utime() path?
> Yes.
Progress <wink>.
...
> Am challenged for time in the next couple of days. Will delve deeper at
> the first opportunity.
>
> For the time being, I think it would be best to use sleep() instead of
> utime(). While it costs three seconds, at least we know it to be a
> platform independent test. It is rather late in the game to be
> debugging OS specific problems introduced by a new check-in.
The checkin isn't that new anymore. Just try changing
past = time.time() - 3
to
past = time.time() - 6
I added a note to <http://www.python.org/1057992> explaining why that
may matter on FAT or FAT32 systems.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4