Project

General

Profile

Actions

action #102227

open

[qe-core] test fails in zypper_lifecycle - Move zypper related tests out of the current scenarios to a gnome only scenario

Added by szarate about 3 years ago. Updated 7 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-11-10
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

At the moment we're running the same tests 48 times, we could move those tests to an extratest_zypper that depends on gnome,

zypper_lifecycle
orphaned_packages_check
zypper_in
zypper_log
zypper_lr
zypper_ref

openQA test in scenario sle-15-SP4-Online-aarch64-gnome+proxy_SCC+allmodules@aarch64 fails in
zypper_lifecycle

curl "https://openqa.suse.de/tests/overview.json?arch=&flavor=&machine=&test=&modules=zypper_lifecycle&module_re=&distri=sle&version=15-SP4&build=61.1&groupid=110#" | jq '.results.sle[][][] | del(.description) | .[].jobid ' | wc -l

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainers: QE Core, jrauch
Install all module which are available through ProxySCC
Install as patterns during installation.

Reproducible

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

Expected result

Last good: 58.2 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (1 open0 closed)

Related to openQA Tests (public) - coordination #95935: [epic][qe-core] Limit installation tests by depending more on the create_hdd_* jobs.New

Actions
Actions #1

Updated by szarate about 3 years ago

  • Related to coordination #95935: [epic][qe-core] Limit installation tests by depending more on the create_hdd_* jobs. added
Actions #2

Updated by punkioudi about 3 years ago

  • Status changed from New to In Progress
  • Assignee set to punkioudi
Actions #3

Updated by punkioudi about 3 years ago

Concerning the fail in zypper_lifecycle, I didn't manage to reproduce it somehow (probably it was a network at the time issue) and in newer builds it doesn't appear at all : https://openqa.suse.de/tests/7715478#step/zypper_lifecycle/52

As for the move of the tests it makes sense. As a first step, I have identified the jobs that the aforementioned modules are running right now :

  • gnome+proxy_SCC+allmodules > x86_64
  • cryptlvm_minimal_x > aarch64
  • cryptlvm_minimal_x > ppc64le
  • cryptlvm_minimal_x > x86_64
  • default > aarch64
  • default > s390x
  • default > x86_64
  • default@64bit-smp > x86_64
  • default@ppc64le-2g > ppc64le
  • default@svirt-hyperv > x86_64
  • default@svirt-hyperv-uefi > x86_64
  • default@uefi > x86_64
  • gnome > aarch64
  • gnome > s390x
  • gnome > x86_64
  • gnome@ppc64le-2g > ppc64le
  • gnome@s390x-kvm-sle15 > s390x
  • gnome@uefi > x86_64
  • gnome+acpi > aarch64
  • gnome+proxy_SCC+allmodules > s390x
  • gnome+proxy_SCC+allmodules > aarch64
  • gnome+proxy_SCC+allmodules > x86_64
  • gnome+proxy_SCC+allmodules@ppc64le-2g > ppc64le
  • minimal+base > s390x
  • minimal_x > aarch64
  • minimal_x > ppc64le
  • minimal_x > s390x
  • minimal_x > x86_64
  • minimal_x+uefi > aarch64
  • minimal_x+uefi@uefi > x86_64
  • system_performance > aarch64
  • textmode+role_kvm > x86_64
  • textmode+role_textmode > aarch64
  • textmode+role_textmode > ppc64le
  • textmode+role_textmode > s390x
  • textmode+role_textmode > x86_64
  • textmode+role_xen > x86_64
  • videomode_text+textmode+role_kvm > x86_64
  • videomode_text+textmode+role_xen > x86_64
  • we-module@64bit-2gbram > x86_64
  • wsm+dev_tools+textmode > aarch64
  • wsm+dev_tools+textmode > ppc64le
  • wsm+dev_tools+textmode > s390x
  • wsm+dev_tools+textmode > x86_64
  • xen > x86_64
Actions #4

Updated by tjyrinki_suse about 3 years ago

  • Parent task set to #98286
Actions #6

Updated by punkioudi almost 3 years ago

  • Target version deleted (QE-Core: Ready)

I will move it out of the sprint, as it's been a long time since I have done the PR and I would like firstly to discuss it with the team, before it gets merged.

Actions #7

Updated by punkioudi almost 2 years ago

  • Assignee deleted (punkioudi)
Actions #8

Updated by slo-gin 9 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #9

Updated by mgrifalconi 7 months ago

  • Status changed from In Progress to Feedback

is this still a current issue? can we close it?

Actions

Also available in: Atom PDF