
report at bugs
Nov 1, 2009, 7:31 AM
Post #11 of 13
(587 views)
Permalink
|
|
[issue6896] Intermittent failures in test_mailbox
[In reply to]
|
|
Antoine Pitrou <pitrou [at] free> added the comment: PS: this is the kind of traces I had when running TestMaildir on David's buildbot: at 1257086460.18, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086459.0 at 1257086460.21, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086459.0 at 1257086460.24, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086459.0 at 1257086460.27, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086459.0 at 1257086460.3, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086459.0 at 1257086460.33, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086459.0 at 1257086460.36, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086460.0 at 1257086460.38, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086460.0 at 1257086460.4, linking/renaming ... mtime of '/home/pitrou/trunk/@test_23145_tmp/new' is now 1257086460.0 As you see, the mtime is set to 1257086459 even when time.time() returns 1257086460.00 and higher, and it's only set to 1257086460 when time.time() reaches 1257086460.36. ---------- _______________________________________ Python tracker <report [at] bugs> <http://bugs.python.org/issue6896> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
|