Project

General

Profile

Actions
Copy link

action #124433

closed

coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5

drop test yast2_http: yast module has been removed

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

Status:
Resolved
Priority:
Normal
Assignee:
leli
Target version:
Current
Start date:
2023-02-14
Due date:
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ncurses@64bit fails in
yast2_http

Test suite description

Maintainer: qsf-y Test for yast2 UI, ncurses only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.
riafarov set TIMEOUT_SCALE to improve stability of the test.

Reproducible

Fails since (at least) Build 20221111

Expected result

Last good: 20210718 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to qe-yam - action #119455: [y][ppc64le] test fails in yast2_dns_server as "do not start on boot" is not selected in pull down menuResolved2022-10-26

Actions
Actions
Copy link
 #1

Updated by dimstar about 1 year ago

also yast2-dns-server and yast2-dhcp-server are being removed (unmaintained)

Actions
Copy link
 #3

Updated by maritawerner about 1 year ago

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

Updated by openqa_review about 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_ncurses
https://openqa.opensuse.org/tests/3150842#step/yast2_rmt/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #5

Updated by JERiveraMoya about 1 year ago

  • Status changed from New to Workable
  • Target version set to Current
  • Parent task set to #121876

I checked with YaST team they told me they cannot drop stuff from SLE between service packs, they have to wait to the next major version.
We will be creating additional schedules for Leap (look like it is needed).

Actions
Copy link
 #6

Updated by leli about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to leli
Actions
Copy link
 #7

Updated by JERiveraMoya about 1 year ago

  • Related to action #119455: [y][ppc64le] test fails in yast2_dns_server as "do not start on boot" is not selected in pull down menu added
Actions
Copy link
 #9

Updated by leli about 1 year ago

  • Status changed from In Progress to Resolved

PR merged.

Actions
Copy link
 #10

Updated by openqa_review about 1 year ago

  • Status changed from Resolved to Feedback

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_ncurses
https://openqa.opensuse.org/tests/3209490#step/yast2_rmt/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #11

Updated by leli about 1 year ago

  • Status changed from Feedback to Resolved

openqa_review wrote:

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_ncurses
https://openqa.opensuse.org/tests/3209490#step/yast2_rmt/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

The failure in the job has nothing related with this ticket.

Actions
Copy link
 #12

Updated by openqa_review about 1 year ago

  • Status changed from Resolved to Feedback

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_ncurses
https://openqa.opensuse.org/tests/3235284#step/yast2_rmt/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #13

Updated by leli about 1 year ago

  • Status changed from Feedback to Resolved

openqa_review wrote:

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_ncurses
https://openqa.opensuse.org/tests/3235284#step/yast2_rmt/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

The failure is nothing related with the ticket, please file a new ticket for it.

Actions
Copy link
 #14

Updated by openqa_review 12 months ago

  • Status changed from Resolved to Feedback

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_ncurses
https://openqa.opensuse.org/tests/3264694#step/yast2_rmt/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #15

Updated by leli 12 months ago

  • Status changed from Feedback to Resolved

The failure is nothing related with the ticket, please file a new ticket for it.

Actions
Copy link

Also available in: Atom PDF