On Jul 21 16:02, David Allsopp wrote:
> Corinna Vinschen wrote:
> > Sent: 21 July 2021 10:33
> > To: cygwin-patches@cygwin.com
> > Subject: Re: Fix nanosleep returning negative rem
> >
> > On Jul 21 11:30, Corinna Vinschen wrote:
> > > I wrote a qu
> I can get it easily get this on my desktop (AMD Ryzen Threadripper 3990X) but
> not at all on my laptop (Intel Core i7-8650U)
Not sure if that's really related but:
Have you checked what is your default Windows timer resolution? Some
applications change it from the default
100HZ to 1000HZ
On Jul 21 11:30, Corinna Vinschen wrote:
> I wrote a quick STC using the NT API calls and I can't reproduce the
> problem with this code either. The output is either
>
> SignalState: 1 TimeRemaining: -5354077459183
>
> or
>
> SignalState: 0 TimeRemaining: 653
>
> I never get a small
On Jul 21 09:07, David Allsopp wrote:
> > On Jul 20 16:16, David Allsopp wrote:
> > > I've pushed a repro case for this to
> > > https://github.com/dra27/cygwin-nanosleep-bug.git
> > >
> > > Originally noticed as the main CI system for OCaml has been failing
> > > sporadically for the signal.ml
> On Jul 20 16:16, David Allsopp wrote:
> > I've pushed a repro case for this to
> > https://github.com/dra27/cygwin-nanosleep-bug.git
> >
> > Originally noticed as the main CI system for OCaml has been failing
> > sporadically for the signal.ml test mentioned in that repo. This
> > morning I
Hi David,
On Jul 20 16:16, David Allsopp wrote:
> I've pushed a repro case for this to
> https://github.com/dra27/cygwin-nanosleep-bug.git
>
> Originally noticed as the main CI system for OCaml has been failing
> sporadically for the signal.ml test mentioned in that repo. This morning I
> tried
I've pushed a repro case for this to
https://github.com/dra27/cygwin-nanosleep-bug.git
Originally noticed as the main CI system for OCaml has been failing
sporadically for the signal.ml test mentioned in that repo. This morning I
tried hammering that test on my dev machine and discovered that it
