Project

General

Profile

Actions

action #134114

closed

coordination #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

Added by tinita 7 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

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 #1

Updated by okurz 7 months ago

  • Due date deleted (2023-08-23)
  • Target version changed from Ready to future
  • Start date deleted (2023-05-20)
Actions #2

Updated by tinita 7 months 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

Actions #3

Updated by tinita 7 months ago

https://github.com/os-autoinst/openQA/pull/5287 Remove defaults, should be ensured by OpenQA::Setup already

Actions #4

Updated by openqa_review 7 months ago

  • Due date set to 2023-09-01

Setting due date based on mean cycle time of SUSE QE Tools

Actions #5

Updated by tinita 7 months ago

  • Status changed from In Progress to Feedback
Actions #6

Updated by tinita 7 months ago

  • Status changed from Feedback to Resolved
Actions #7

Updated by okurz 5 months ago

  • Due date deleted (2023-09-01)
Actions

Also available in: Atom PDF