action #180026
Updated by okurz about 1 month ago
## Observation From #176148-25 CI tests on github one statistics run shows 24 fails with "(Wstat: 139 Tests: 12 Failed: 0)" in https://github.com/okurz/Mojo-IOLoop-ReadWriteProcess/actions/runs/14220387974/job/39864871854#step:6:27156 that is a fail ratio of 2.40±.94% whereas other runs are 100.00% stable, e.g. Perl 5.26 based run https://github.com/okurz/Mojo-IOLoop-ReadWriteProcess/actions/runs/14220387974/job/39864871866. The Perl version does not seem to have an impact but likely the load on the node running tests, e.g. less load likely producing no failures and higher load more likely to cause problems. Code "139" means segmentation fault so I assume either in this module or any other module we use unclean memory handling during termination. ## Acceptance Criteria * **AC1:** CI statistic runs show no "(Wstat: 139 Tests: … Failed: 0)" from t/01_run.t * **AC2:** No workaround retries in CI definition, e.g. from https://github.com/openSUSE/Mojo-IOLoop-ReadWriteProcess/pull/79 ## Suggestions * Look into how to best debug Perl segfaults within github actions * Ensure stability * Remove any workarounds, e.g. retries, in place