Project

General

Profile

Actions

action #115814

closed

Record soft-failure in test suite installer_extended for product modules not available in early phase

Added by rainerkoenig over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
Start date:
2022-08-26
Due date:
% Done:

0%

Estimated time:

Description

Observation

Failing openQA jobs: https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=installer_extended&modules=&module_re=&distri=sle&version=15-SP5&build=25.1&groupid=129#
The list of expected modules (alphabetically sorted) is:

PackageHub
sle-ha
sle-module-NVIDIA-compute
sle-module-basesystem
sle-module-certifications
sle-module-containers
sle-module-desktop-applications
sle-module-development-tools
sle-module-legacy
sle-module-live-patching
sle-module-public-cloud
sle-module-python3
sle-module-server-applications
sle-module-transactional-server
sle-module-web-scripting
sle-we

The missing modules are PackageHub, sle-module-NVIDIA-compute and sle-module-certifications.

In the same way that with other task, we should try to avoid failures of this kind where the result cannot be predicted easily, in the sense that we don't know when this package will be available, could be in beta or could be a bit later. For that instead of having failure we will marking the job with soft-failure and then with very few failures we will be able to pay more attention to soft-failures.

Acceptance criteria

AC1: File a bug for this if doesn't exist
AC2: Improve existing die adding list of product module mismatching
AC3: Record soft-failure instead of using die when the product module list mismatching is the subset identified above.

Additional info

User function arrays_subset in utils.pm to actually give an error message with the mismatch.
Use the very same function to decide if die or soft-fail depending on the list of modules mismatching.

Actions #1

Updated by JERiveraMoya over 1 year ago

  • Tags set to qe-yast-refinement
  • Subject changed from Installer_extended test suite fails because of missing modules to Record soft-failure in test suite installer_extended for product modules not available in early phase
  • Description updated (diff)
  • Priority changed from Normal to High
  • Target version set to Current
Actions #2

Updated by coolgw over 1 year ago

I prefer using bug flag case firstly, keep red alarm in openqa since this fail only impact installer_extended.

Actions #3

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #4

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #5

Updated by JERiveraMoya over 1 year ago

coolgw wrote:

I prefer using bug flag case firstly, keep red alarm in openqa since this fail only impact installer_extended.

The problem with the flag is that is not perfect, here when someone check this will not include label with a bug for the cases where there is an infrastructure problem. Next reviewer will check this and will need to see if applies and add the bug label once the infra issue is solved. IMO there is a bit of human handling here that is actually not needed, because it is expected that this modules are not there at the beginning, it is a test without clear expectations, because the product is in development phase so we need to relax the expectation and not fail.

Another point that I will like to see in the future is that when you navigate to: https://openqa.suse.de/group_overview/129
right now you see 47 failures, what if, the failures displayed there would be just the ones meaningful to you.
For that we need more soft-failures, more 'moving to dev group' and of course as ultimate thing, when a failure happens in several archs, the test case is similar in all of them (as it should be) disable all the archs except one, then we will have an exact number of failures, giving us a more realistic view of results.

Actions #6

Updated by JERiveraMoya over 1 year ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions #7

Updated by JERiveraMoya over 1 year ago

  • Tags set to qe-yast-refinement
  • Description updated (diff)
  • Status changed from Workable to New
Actions #8

Updated by JERiveraMoya over 1 year ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions #9

Updated by coolgw over 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to coolgw
Actions #11

Updated by JERiveraMoya over 1 year ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF