action #95851
Updated by tinita over 3 years ago
## Problem
t/43-scheduling-and-worker-scalability.t fails more often than it used too (it is in "unstable" already)
https://app.circleci.com/pipelines/github/os-autoinst/openQA/7142/workflows/7a75593c-a719-4da8-934e-4c4433f67dc2/jobs/67405/steps
```
[10:02:57] t/43-scheduling-and-worker-scalability.t .. 1/?
# Failed test 'all jobs done'
# at t/43-scheduling-and-worker-scalability.t line 218.
# got: '4'
# expected: '5'
# Failed test 'all jobs passed'
# at t/43-scheduling-and-worker-scalability.t line 219.
# got: '4'
# expected: '5'
# All jobs:
# - id: 1, state: done, result: passed, reason: none
# - id: 2, state: done, result: passed, reason: none
# - id: 3, state: done, result: passed, reason: none
# - id: 4, state: done, result: passed, reason: none
# - id: 5, state: running, result: none, reason: none
# Looks like you failed 2 tests of 3.
[10:02:57] t/43-scheduling-and-worker-scalability.t .. 2/?
# Failed test 'assign and run jobs'
# at t/43-scheduling-and-worker-scalability.t line 221.
[10:02:57] t/43-scheduling-and-worker-scalability.t .. 3/? # Looks like you failed 1 test of 4.
[10:02:57] t/43-scheduling-and-worker-scalability.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/4 subtests
```
## Acceptance Criteria
**AC 1**: t/43-scheduling-and-worker-scalability.t is stable for the next 10 runs after applying the solution
## Suggestions
* Just an observation: It became more unstable when many of our tests on CircleCI became slower and unstable
* Only can be reproduced on CircleCI
* Could be a timing time problem
* Consider the slowdown of collecting code coverage being a problem, especially problem specially regarding forking