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 and thanks for accepting the script.
Please feel free to suggest changes to turn on additional tests etc.
Will do.
I'll add a check for unexpected "panic" output from Cygwin to report
failure then. Example:
$ ./cygstress dev
>>> SUCCESS: dev
>>> SUCCESS: All 1 stress test(s) succeeded
$ stress-ng --dev 1 -t 1
stress-ng: info: [40534] setting to a 1 sec run per stressor
stress-ng: info: [40534] dispatching hogs: 1 dev
0 [main] stress-ng 40537 C:\cygwin64\bin\stress-ng.exe: \
*** fatal error in forked process -
pthread_mutex::_fixup_after_fork \
() doesn't understand PROCESS_SHARED mutex's
... etc ...
stress-ng: info: [40534] skipped: 0
stress-ng: info: [40534] passed: 1: dev (1)
stress-ng: info: [40534] failed: 0
stress-ng: info: [40534] metrics untrustworthy: 0
stress-ng: info: [40534] successful run completed in 1.17 sec
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?
--
Regards,
Christian
