Actions
action #95263
open[beginner] t/44-scripts.t times out in circleCI after 420s - skip coverage analysis in this test?
Start date:
2021-07-09
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
[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 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
Further details¶
Entrance level issue
Updated by okurz over 3 years ago
- Status changed from New to Feedback
- Assignee set to okurz
nah, we have better things to do. I will just bump the timeout again for now: https://github.com/os-autoinst/openQA/pull/4029
Updated by okurz about 3 years ago
- Description updated (diff)
- Category changed from Regressions/Crashes to Feature requests
- Status changed from Feedback to New
- Assignee deleted (
okurz) - Priority changed from High to Low
- Target version changed from Ready to future
Updated by okurz over 2 years ago
- Tags set to beginner, entrance level issue
- Subject changed from t/44-scripts.t times out in circleCI after 420s - skip coverage analysis in this test? to [beginner] t/44-scripts.t times out in circleCI after 420s - skip coverage analysis in this test?
- Description updated (diff)
Actions