Project

General

Profile

Actions
Copy link

action #125759

closed

fail in yast2_bootloader does not produce yast logs for the test

Added by dimstar about 1 year ago. Updated 11 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2023-03-10
Due date:
% Done:

0%

Estimated time:

Description

Observation

This ticket is not about the failure per se, but rather about the fact that the test does not upload y2log files after a yast failure is detected.
Any bug report given to the YaST Team requires the logs for proper progress. There are a lot of times when openQA does upload y2log files, so it would be verified/fixed to happen in all yast cases.

openQA test in scenario opensuse-Tumbleweed-LegacyX86-DVD-i586-gnome@32bit fails in
yast2_bootloader

Test suite description

Revert schedule to working settings - dleuenberger, 20211117

Reproducible

Fails since (at least) Build 20230309 (current job)

Expected result

Last good: 20230308 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by maritawerner about 1 year ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
Actions
Copy link
 #2

Updated by JERiveraMoya 11 months ago

  • Status changed from New to Rejected

This is not failing anymore: https://openqa.opensuse.org/tests/3350151#step/yast2_bootloader/4
This issue is quite common, we need to tackle case by case, depending on the type of failure and the kind of legacy code we have for each module.

This is one of the legacy test module using needles and shortcuts, we still have it in SLE because it didn't give us any trouble, but we will be deprecating it once we extend a bit more this one based on libyui-rest-api, https://openqa.suse.de/tests/11175388#step/bootcode_options/6, the focus of Yam squad is is installation and migrations and we get some time for something else like the YaST modules, we would only be tackle the ones developed in libyui-rest-api or converting them, so only those could get some improvement with the unfortunately complex class hierarchy that exist in Perl in the repo to retrieve logs. For ALP we are trying to keep an eye of reducing the amount of classes for log retrieval.

Anyway please file a ticket case by case if you find other cases (because we are aware of this issue of bugs without logs) and we can consider the effort on fixing legacy test or creating new ones.

Actions
Copy link

Also available in: Atom PDF