On 03/05/2025 12:20, Jon Turney wrote:
On 27/04/2025 22:20, Jeremy Drake via Cygwin-patches wrote:
On Sun, 27 Apr 2025, Jon Turney wrote:
Use an output variable from cygwin-install-action to inform where we
unpack the just-built cygwin artifact, because apparently the Windows
ARM64 runners have a different configuration (no D: drive).
I applied this, but there seems to be some flakiness in the stress-ng
tests when run on arm64, so I then tweaked it to ignore failures on
arm64, for the moment.
(not idea, but is probably what I should have done in the first place
until I had a bit more of a baseline for how this test behaves).
I have seen the 'kill' and 'alarm' stress-ng tests sometimes fail on
arm64. I'm sure this is a bug in Cygwin somewhere, but investigating it
isn't easy without the hardware...
