Project

General

Profile

Actions

action #115712

closed

Move very slow installation with svirt-hyperv-* to development group

Added by hjluo over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-08-25
Due date:
% Done:

0%

Estimated time:

Description

Motivation

During whole SP SLE-15-SP4 we have seen this behavior in svirt-hyperv and along with the other issue with the serial we have been sharing this with other stakeholders. For SLE-15-SP5 we will do the same but we will not run this in YaST group, but in a development group.

See the following jobs:

https://openqa.nue.suse.com/tests/9381738
https://openqa.nue.suse.com/tests/9381497

which failed at perform_installation not finishing in more than 4 hours.
the value for timeout scale is already on 6 (which is too much), we should move these test to the development group.
We should revisit all these test cases for svirt-hyperv and collect all that present this behavior.

Acceptance criteria

AC1: svirt-hyperv-* test suites which sporadically take 4 hours to complete are not running in YaST group.

Suggestions

If we haven't finish yet #115235 we have this dev group since a lot of time ago, https://openqa.suse.de/group_overview/96 afir it is control version (by Core squad?) We have to find a temporary place but should be under git to not loose any information.

Actions #1

Updated by JERiveraMoya over 2 years ago

  • Tags set to qe-yast-refinement
  • Project changed from openQA Tests (public) to qe-yam
  • Subject changed from Move yast group perform_installation failed cases to development group to Move very slow installation with svirt-hyperv-* to development group
  • Description updated (diff)
  • Target version set to Current
Actions #2

Updated by JERiveraMoya over 2 years ago

  • Description updated (diff)
Actions #3

Updated by JERiveraMoya over 2 years ago

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

Updated by shukui over 2 years ago

  • Assignee set to shukui
Actions #5

Updated by JERiveraMoya over 2 years ago

  • Status changed from Workable to In Progress
Actions #7

Updated by shukui over 2 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF