Christian Franke wrote:
Jon Turney wrote:
...
Any insight into what's going on with the 'clock' test?
No, as I could not reproduce it (on a real machine) yet. Possibly an
effect which only happens if run in a VM?
It possibly only happens when run with admin privileges. Is this the
case
Jon Turney wrote:
On 20/04/2025 20:25, Jon Turney wrote:
Jon Turney (4):
Cygwin: CI: Pass the just-built cygwin to a subsequent job
Cygwin: CI: Run stress-ng
Cygwin: CI: Make stress test terser
Cygwin: CI: Disable stress-ng clock test
OK, I pushed v2 of this.
Sorry for the delay
On 20/04/2025 20:25, Jon Turney wrote:
Jon Turney (4):
Cygwin: CI: Pass the just-built cygwin to a subsequent job
Cygwin: CI: Run stress-ng
Cygwin: CI: Make stress test terser
Cygwin: CI: Disable stress-ng clock test
OK, I pushed v2 of this.
Please feel free to suggest changes to t
On 15/04/2025 18:50, Jeremy Drake via Cygwin-patches wrote:
On Fri, 11 Apr 2025, Jon Turney wrote:
Jon Turney (4):
Cygwin: CI: Pass the just-built cygwin to a subsequent job
Cygwin: CI: Run stress-ng
Cygwin: CI: Make stress test terser
Cygwin: CI: Disable stress-ng clock test
FY
On Fri, 11 Apr 2025, Jon Turney wrote:
>
> Jon Turney (4):
> Cygwin: CI: Pass the just-built cygwin to a subsequent job
> Cygwin: CI: Run stress-ng
> Cygwin: CI: Make stress test terser
> Cygwin: CI: Disable stress-ng clock test
FYI, as of 4/14, GitHub has *finally* put a Windows ARM64 r
