Cygwin: CI: Disable stress-ng clock testHEADgithub/mastergithub/mainmastermain

> stress-ng: 23:25:43.13 debug: [1338] invoked with 'stress-ng -v -M --oomable --timestamp --verify --temp-path /cygdrive/c/Users/RUNNER~1/AppData/Local/Temp/stress-ng.1237.5.d -t 5 --log-file /cygdrive/d/a/cygwin/cygwin/logs/clock --clock 2' by user 197108 'runneradmin'
> stress-ng: 23:25:43.14 debug: [1338] stress-ng 0.18.12
> stress-ng: 23:25:43.15 debug: [1338] system: CYGWIN_NT-10.0-20348 fv-az2222-241 3.7.0-api-358.x86_64 2025-04-10 23:13 UTC x86_64, gcc 12.4.0, Cygwin libc, little endian
> stress-ng: 23:25:43.15 debug: [1338] RAM total: 16.0G, RAM free: 13.8G, swap free: 2.9G
> stress-ng: 23:25:43.15 debug: [1338] temporary file path: '/cygdrive/c/Users/runneradmin/AppData/Local/Temp/stress-ng.1237.5.d'
> stress-ng: 23:25:43.15 debug: [1338] 4 processors online, 4 processors configured
> stress-ng: 23:25:43.15 info:  [1338] setting to a 5 secs run per stressor
> stress-ng: 23:25:43.15 debug: [1338] cache allocate: using defaults, cannot determine cache level details
> stress-ng: 23:25:43.15 debug: [1338] cache allocate: shared cache buffer size: 2048K
> stress-ng: 23:25:43.15 info:  [1338] dispatching hogs: 2 clock
> stress-ng: 23:25:43.15 debug: [1338] starting stressors
> stress-ng: 23:25:43.17 debug: [1338] 2 stressors started
> stress-ng: 23:25:43.41 debug: [1340] clock: [1340] started (instance 0 on CPU 2)
> stress-ng: 23:25:43.43 debug: [1341] clock: [1341] started (instance 1 on CPU 2)
> stress-ng: 00:00:00.-99 fail:  [1340] clock: clock_settime was able to set an invalid negative time for timer 'CLOCK_REALTIME'
> stress-ng: 00:00:00.-99 fail:  [1340] clock: clock_settime was able to set an invalid negative time for timer 'CLOCK_REALTIME_COARSE'
> stress-ng: 00:00:00.-99 fail:  [1341] clock: clock_settime was able to set an invalid negative time for timer 'CLOCK_REALTIME'
> stress-ng: 00:00:00.-99 fail:  [1341] clock: clock_settime was able to set an invalid negative time for timer 'CLOCK_REALTIME_COARSE'
> stress-ng: 23:25:48.39 debug: [1340] clock: [1340] exited (instance 0 on CPU 2)
> stress-ng: 23:25:48.39 error: [1338] clock: [1340] terminated with an error, exit status=2 (stressor failed)
> stress-ng: 23:25:48.39 debug: [1338] clock: [1340] terminated (stressor failed)
> stress-ng: 23:25:48.40 debug: [1341] clock: [1341] exited (instance 1 on CPU 2)
> stress-ng: 23:25:48.40 error: [1338] clock: [1341] terminated with an error, exit status=2 (stressor failed)
> stress-ng: 23:25:48.40 debug: [1338] clock: [1341] terminated (stressor failed)
> stress-ng: 23:25:48.40 debug: [1338] metrics-check: all stressor metrics validated and sane
> stress-ng: 23:25:48.41 metrc: [1338] stressor       bogo ops real time  usr time  sys time   bogo ops/s     bogo ops/s CPU used per       RSS Max
> stress-ng: 23:25:48.41 metrc: [1338]                           (secs)    (secs)    (secs)   (real time) (usr+sys time) instance (%)          (KB)
> stress-ng: 23:25:48.41 metrc: [1338] clock            158338      4.97      1.48      7.11     31888.38       18428.54        86.52         19992
> stress-ng: 23:25:48.41 info:  [1338] skipped: 0
> stress-ng: 23:25:48.41 info:  [1338] passed: 0
> stress-ng: 23:25:48.41 info:  [1338] failed: 2: clock (2)
> stress-ng: 23:25:48.41 info:  [1338] metrics untrustworthy: 0
> stress-ng: 23:25:48.41 info:  [1338] unsuccessful run completed in 5.25 secs
>>>> FAILURE: clock (exit status 2)

0 files changed, 0 insertions, 0 deletions