action #81150
Updated by okurz over 3 years ago
## Observation Observed in https://github.com/os-autoinst/os-autoinst/pull/1606 and previously in another PR unrelated to t/10-virtio_terminal.t ## Steps to reproduce Using https://github.com/okurz/scripts/tree/master/count_fail_ratio ``` env runs=4000 runs=400 count_fail_ratio prove -I. t/10-virtio_terminal.t ``` ## Problem The "Steps to reproduce" show 4/4000 fails for okurz, showing ``` t/10-virtio_terminal.t .. Bailout called. Further testing stopped: test exceeds runtime limit of '10' seconds Timeout for pipe other side helper at t/10-virtio_terminal.t line 33. FAILED--Further testing stopped: test exceeds runtime limit of '10' seconds ``` so a fail rate of only 0.1%. Likely depending on timing behaviour this can happen more often, e.g. in GHA or when running with coverage analysis enabled. Line 33 is an internal alarm handler. Because we try to use an alarm handler for the overall test module timeout here as well this might cause conflicts.