action #124433
closedcoordination #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 almost 1 year ago.
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
Updated by dimstar about 1 year ago
also yast2-dns-server and yast2-dhcp-server are being removed (unmaintained)
Updated by dimstar about 1 year ago
Updated by maritawerner about 1 year ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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).
Updated by leli about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to leli
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
Updated by leli about 1 year ago
PR submitted: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16580
PR submitted for test suites: https://github.com/os-autoinst/opensuse-jobgroups/pull/285
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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/1To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234Expect 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.
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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/1To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234Expect 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.
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/3264694#step/yast2_rmt/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by leli almost 1 year ago
- Status changed from Feedback to Resolved
The failure is nothing related with the ticket, please file a new ticket for it.