On Wednesday 11 August 2021 at 18:32:31 +0200, Alexander Kanavin wrote:
> On Wed, 11 Aug 2021 at 18:14, Mike Crowe wrote:
> > I agree regarding the lack of explanation. However, even if the problem is
> > real (which it looks like it is based on
> > https://bugs.python.org/issue41710)
> > then it
On Wed, 11 Aug 2021 at 18:14, Mike Crowe wrote:
> I agree regarding the lack of explanation. However, even if the problem is
> real (which it looks like it is based on
> https://bugs.python.org/issue41710)
> then it wouldn't be expected to cause test failures unless the system clock
> was being
On Wednesday 11 August 2021 at 13:36:23 +0200, Alexander Kanavin wrote:
> I too do not think this is sufficiently explained. All of python ptests
> pass, so there needs to be a demonstrator of incorrect behavior, or let's
> just revert it.
I agree regarding the lack of explanation. However, even
I too do not think this is sufficiently explained. All of python ptests
pass, so there needs to be a demonstrator of incorrect behavior, or let's
just revert it.
Alex
On Mon, 9 Aug 2021 at 19:53, Ross Burton wrote:
> On Tue, 3 Aug 2021 at 05:41, Zhang, Qiang
> wrote:
> > The timeout for
On Tue, 3 Aug 2021 at 05:41, Zhang, Qiang wrote:
> The timeout for threading.Lock, threading.Condition, etc, is not using
> a monotonic clock, it is affected if the system time (realtime clock)
> is set.
>
> This patch will make condvar use monotonic clock.
> Refence:
On Mon, Aug 2, 2021 at 6:41 PM Zhang, Qiang wrote:
>
> From: Zqiang
>
> The timeout for threading.Lock, threading.Condition, etc, is not using
> a monotonic clock, it is affected if the system time (realtime clock)
> is set.
>
> This patch will make condvar use monotonic clock.
> Refence:
