[issue24707] Assertion failed in pymonotonic_new

STINNER Victor added the comment: I removed the assertion. Thanks for your report! -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue24707] Assertion failed in pymonotonic_new

Roundup Robot added the comment: New changeset 4c90b4a4fffa by Victor Stinner in branch '3.5': Issue #24707: Remove assertion in monotonic clock https://hg.python.org/cpython/rev/4c90b4a4fffa -- nosy: +python-dev ___ Python tracker

[issue24707] Assertion failed in pymonotonic_new

STINNER Victor added the comment: It occurred on more time on the same buildbot: http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.x/builds/2569/steps/test/logs/stdio -- ___ Python tracker _

[issue24707] Assertion failed in pymonotonic_new

STINNER Victor added the comment: IMHO the best to do with this issue is to document that Python doesn't ensure that the clock is monotonic, but only exposes what the OS provides, and then remove the assertion. -- ___ Python tracker

[issue24707] Assertion failed in pymonotonic_new

STINNER Victor added the comment: Hum, I'm not sure that I was clear: in fact, the assertion is only useful for me, because I'm curious to know bugs in implementations of monotonic clocks. In the case of this buildbot, it may be a bug in qemu, less likely in the linux kernel. I don't think that

[issue24707] Assertion failed in pymonotonic_new

Chris Angelico added the comment: Ah. It's one of *those* bugs. Got it. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue24707] Assertion failed in pymonotonic_new

STINNER Victor added the comment: Chris Angelico added the comment: > Where's this issue heading? The buildbots seem to be green now, does that > imply that this is fixed? The issue still exist, it's just that the issue occurs randomly and is very rare (seen twice in 6 months...). --

[issue24707] Assertion failed in pymonotonic_new

Chris Angelico added the comment: Where's this issue heading? The buildbots seem to be green now, does that imply that this is fixed? -- ___ Python tracker ___ _

[issue24707] Assertion failed in pymonotonic_new

Chris Angelico added the comment: The host is running Debian Jessie (newer than the Debian Wheezy of the VM). Linux sikorsky 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux What info are you after re hardware virtualization? VirtualBox 4.3.28 r100309 manages th

[issue24707] Assertion failed in pymonotonic_new

Changes by STINNER Victor : -- nosy: +Rosuav ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue24707] Assertion failed in pymonotonic_new

Changes by STINNER Victor : -- nosy: -Chris ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue24707] Assertion failed in pymonotonic_new

STINNER Victor added the comment: This buildbot runs in a VM. I need more information on the host (machine running the VM): OS, OS version, kernel version, hardware virtualization?, version of qemu/kvm?, etc. It's probably a bug in the virtualization. In the PEP 418, we decided to _not_ handl

[issue24707] Assertion failed in pymonotonic_new

New submission from Berker Peksag: >From >http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.x/builds/2436: python: Python/pytime.c:633: pymonotonic_new: Assertion `!last_set || last <= *tp' failed. Fatal Python error: Aborted Full log is here: http://buildbot.python.org/all/b