action #102221
Updated by livdywan over 2 years ago
## Observation
Running t/25-cache-service.t locally for me consistently fails with
```
ok 10 - Asset sle-12-SP3-x86_64-0368-200_88888@64bit.qcow2 downloaded correctly
ok 11 - Asset sle-12-SP3-x86_64-0368-200_88888@64bit.qcow2 downloaded correctly
ok 12 - Asset sle-12-SP3-x86_64-0368-200_88888@64bit.qcow2 downloaded correctly
<5>[26308] [i] Worker 26308 stopped
# Cache minion worker stopped
<5>[26309] [i] Worker 26309 stopped
# Cache minion worker stopped
Bailout called. Further testing stopped: test 't/25-cache-service.t' exceeds runtime limit of '90' seconds
Bail out! test 't/25-cache-service.t' exceeds runtime limit of '90' seconds
FAILED--Further testing stopped: test 't/25-cache-service.t' exceeds runtime limit of '90' seconds
```
I ran `count_fail_ratio prove -l -v t/25-cache-service.t` using https://github.com/okurz/scripts/blob/master/count_fail_ratio with default 20 runs and all 20 runs fail consistently in the above step.
## Problem
circleCI already runs Leap 15.3 as well https://github.com/os-autoinst/openQA/blob/master/container/devel:openQA:ci/base/Dockerfile#L7 and that works just fine there. If I bump the timeout 90s->300s then tests pass fine.
## Acceptance criteria
- **AC1**: Time limit of 90s is not exceeded
## Suggestions
- Run I just ran these tests after upgrading to Leap 15.3 so I don't know if the same happened in a clean container e.g. `toolbox -u -i registry.opensuse.org/opensuse/leap:15.3 -t leap15.3` or similar
- Maybe files left over from another test run?
- Consider a `git status` check like we have before. Would be good if others could just crosscheck how it behaves for os-autoinst
- Investigate what's slowing the test down e.g. bisect test runtime from when the timeout was introduced or changed them.