Project

General

Profile

Actions

action #122296

open

Fix openqa-trigger-bisect-jobs to actually remove incidents from bisection tests again

Added by okurz almost 2 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-02-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Originally brought up in #97118#note-10 by okurz and mgrifalconi.
https://github.com/os-autoinst/scripts/blob/master/openqa-trigger-bisect-jobs originally removed individual incidents from a list to conduct tests excluding specific incidents to be able to bisect with/without individual incidents. Seems like something was changed in the test architecture to install all updates in the image generation jobs meaning that the repos and packages from the repos are not removed by just changing the test variable content within bisection jobs. The test code needs to be changed to account for that. Maybe as simple as removing the according zypper repo and calling zypper dup or zypper rm or something.

Impact

All results of "openqa-trigger-bisect-jobs" are invalid as the mentioned incidents are not actually excluded. Without correct results also "openqa-trigger-bisect-jobs" can not be used for any automatic decisions which would help in the daily work of openQA reviewers concerning SLE maintenance update testing.

Acceptance criteria

Suggestions


Related issues 3 (1 open2 closed)

Related to QA (public) - action #97118: enhance bot automatic approval: check multiple daysResolvedmgrifalconi2021-08-18

Actions
Related to openQA Project (public) - action #131204: openqa-trigger-bisect-jobs is called on passed jobs size:MResolveddheidler2023-06-212023-07-04

Actions
Blocks openQA Tests (public) - action #124370: [qe-core] geekotest bisect is not removing the issue from all test repositoriesBlockedszarate2023-02-13

Actions
Actions

Also available in: Atom PDF