Project

General

Profile

Actions

action #116251

open

Missing traceback in when no needle matches

Added by ph03nix about 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
QA (public, currently private due to #173521) - future
Start date:
2022-09-06
Due date:
% Done:

0%

Estimated time:

Description

Observation

When a test dies because of a needle mismatch, there is no traceback (as it is in other test failures), which makes it sometimes difficult to determine, where the needle mismatch happened.

e.g. # Test died: no candidate needle with tag(s) 'grub2' matched - https://duck-norris.qam.suse.de/tests/10585#step/cockpit_service/34

On other test failures there is typically a traceback attached to the failure, which is helpful to determine the exact location of the arising issue

Steps to reproduce

  • Create a needle mismatch

Impact

  • Determination of where the needle mismatch happens is often cumbersome.

Problem

See Observation

Suggestion

  • Print a traceback on needle mismatches.

Workaround

  • Use the autoinst-log.txt and try to figure out the location therein.

Files

no_traceback.png (128 KB) no_traceback.png ph03nix, 2022-09-06 06:28
traceback.png (174 KB) traceback.png ph03nix, 2022-09-06 06:29
Actions #1

Updated by livdywan about 2 years ago

  • Target version set to future

Discussed briefly, putting to future for now since it's a new feature and may not be trivial

Actions

Also available in: Atom PDF