Project

General

Profile

Actions

action #94880

closed

Carry-over despite mismatch of failing job modules

Added by mkittler over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2021-06-29
Due date:
% Done:

0%

Estimated time:

Description

observation

The comment https://openqa.opensuse.org/tests/1811337#comments has been taken from https://openqa.opensuse.org/tests/1805129 although the job fails in one additional test module.

further information

The current and previous jobs contain both a bug reference within the title of a step of a failed/softfailed module:

rogue workqueue lockup bsc#1126782 - Serial error: [ 5297.323977] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 34s!

(https://openqa.opensuse.org/tests/1805129#step/vhostmd/37)

The code in _failure_reason looks like it would only consider that bug reference then, ignoring the list of actually failed modules. The problematic code has been introduced by https://github.com/os-autoinst/openQA/commit/ef5f07c561cb4bb6139d17b98b616af6b81a8fff so we should take care to still support that use-case.

impact

The release tooling relies on that, if it just ignores failures it can result in broken releases.


Related issues 2 (0 open2 closed)

Related to openQA Project - action #80686: wrong label carry-over to a job where an additional module failed before the one failing in beforeResolvedmkittler2020-12-03

Actions
Related to openQA Project - action #70915: Bugref comments carried over even if status changed failed -> incompleteResolvedmkittler2020-09-03

Actions
Actions

Also available in: Atom PDF