Actions
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
Actions