action #134114
closedcoordination #110833: [saga][epic] Scale up: openQA can handle a schedule of 100k jobs with 1k worker instances
coordination #108209: [epic] Reduce load on OSD
Ensure to call OpenQA::Setup::read_config in unit tests
Description
Motivation¶
In #129619 and the PR https://github.com/os-autoinst/openQA/pull/5279 we saw that inspite of having set a default value for max_running_jobs in OpenQA::Setup, it was undefined in some tests.
As a result, we have to ensure a default whereever we use that config entry, which is sad, because that's not how it's supposed to work and can lead to diverged default values in the worst case.
Acceptance criteria¶
- AC1: Make sure OpenQA::Setup::read_config is called in tests to ensure we get all default config values
Updated by okurz over 1 year ago
- Due date deleted (
2023-08-23) - Target version changed from Ready to future
- Start date deleted (
2023-05-20)
Updated by tinita over 1 year ago
- Status changed from New to In Progress
- Assignee set to tinita
- Target version changed from future to Ready
Since I was already working on this in #129619
Updated by tinita over 1 year ago
https://github.com/os-autoinst/openQA/pull/5287 Remove defaults, should be ensured by OpenQA::Setup already
Updated by openqa_review over 1 year ago
- Due date set to 2023-09-01
Setting due date based on mean cycle time of SUSE QE Tools
Updated by tinita over 1 year ago
- Status changed from In Progress to Feedback
https://github.com/os-autoinst/openQA/pull/5287 merged and deployed on o3