[issue14131] test_threading failure on WIndows 7 3.x buildbot

2013-08-13 Thread STINNER Victor
STINNER Victor added the comment: This failure was not seen recently, let's close this issue. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-03-26 Thread STINNER Victor
STINNER Victor added the comment: > It could be interesting to replace time.time() > by the new time.monotonic(). I changed threading (at least in threading.py) and queue modules to replace time.time() by time.steady() in the issue #14222. Other places in the threading module should be modifi

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-03-26 Thread STINNER Victor
Changes by STINNER Victor : -- Removed message: http://bugs.python.org/msg156882 ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-03-26 Thread STINNER Victor
STINNER Victor added the comment: > It could be interesting to replace time.time() > by the new time.monotonic(). The issue #12822 asks to use monotonic clocks when available. -- nosy: +haypo ___ Python tracker _

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-02-27 Thread Charles-François Natali
Charles-François Natali added the comment: Does Windows still have its once per day/week/whatever time synchronization, or does it use a proper NTP client? Because this offset is way too large for a broken RTC lock, so it might simply be some process adjusting the clock behind our back (althou

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-02-27 Thread Nadeem Vawda
Nadeem Vawda added the comment: A very similar failure in test_thread: http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%203.x/builds/4469/steps/test/logs/stdio -- status: pending -> open ___ Python tracker

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-02-26 Thread Nick Coghlan
Nick Coghlan added the comment: Re: test_packaging: my mistake, the problem was actually test_package__file__ in test_imp (and Antoine already fixed it - there were some caches that weren't getting cleared properly: #14080) The last Win7 test run was green, so we may have to write this one up

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-02-26 Thread Nadeem Vawda
Nadeem Vawda added the comment: This is rather curious. It looks like the assertion includes a (generous) fudge factor in case the timing code is inaccurate, but then the actual time taken is *just* short enough to make it fail. > (the Win7 buildbot for trunk isn't in a good place, with regula

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-02-26 Thread Stefan Krah
Changes by Stefan Krah : -- nosy: +db3l ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-02-26 Thread Stefan Krah
Stefan Krah added the comment: Strange, I can't reproduce this on Windows 7 with exactly the same command line: python_d -Wd -E -bb ../lib/test/regrtest.py -uall -rwW -n -r --randseed=8022149 -- nosy: +skrah ___ Python tracker

[issue14131] test_threading failure on WIndows 7 3.x buildbot

2012-02-26 Thread Nick Coghlan
New submission from Nick Coghlan : http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%203.x/builds/4458/steps/test/logs/stdio Appears to be new, but also isn't obviously related to any recent checkins that I noticed. (the Win7 buildbot for trunk isn't in a good place, with regular