action #95263
Updated by okurz about 3 years ago
## Observation https://app.circleci.com/pipelines/github/os-autoinst/openQA/6978/workflows/9e8ff452-f171-4e7b-a650-e41739505549/jobs/65827?invite=true#step-108-55 ``` [17:29:24] t/44-scripts.t ........ 72/? Bailout called. Further testing stopped: test exceeds runtime limit of '420' seconds FAILED--Further testing stopped: test exceeds runtime limit of '420' seconds ``` Considering that within t/44-scripts.t Should we spawn a lot of processes and collecting coverage for these processes might be already covered by other more specific tests, should we skip coverage analysis in this test? ## Acceptance criteria * **AC1:** t/44-scripts.t is able to finish consistently within a reasonable time within our CI system ## Suggestions * Run `prove -l -v t/44-scripts.t` to find out which components in their take the longest and optimize there * Disable coverage analysis and see what we loose in the overall report * Consider splitting t/44-scripts.t into multiple test scripts