action #108368
open[qe-core] Leap 15.4 test fails in enlightenment_first_start and shutdown re-working needed
0%
Description
Observation¶
Hello seems like there is some pending work on shutdown and first_start after our enlightenment update.
This is a tracker for the work.
I did ping Simon about it.
openQA test in scenario opensuse-15.4-NET-aarch64-otherDE_enlightenment@aarch64 fails in
enlightenment_first_start
Test suite description¶
Reproducible¶
Fails since (at least) Build 119.3
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by szarate about 2 years ago
- Subject changed from Leap 15.4 test fails in enlightenment_first_start and shutdown re-working needed to [qe-core] Leap 15.4 test fails in enlightenment_first_start and shutdown re-working needed
Updated by szarate about 2 years ago
Lubos, when you say that this is a tracker for the work I guess you mean the work to fix it? Also, is Simon (whoever that Simon is :)) going to work on fixing the tests?
Updated by okurz about 2 years ago
szarate wrote:
Also, is Simon (whoever that Simon is :)) going to work on fixing the tests?
that would be "Simon Lees", maintainer of the enlightenment stack in openSUSE, also see
https://en.opensuse.org/Portal:Enlightenment/Team
Updated by openqa_review almost 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: otherDE_enlightenment
https://openqa.opensuse.org/tests/2349203#step/reboot_icewm/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 32 days if nothing changes in this ticket.
Updated by slo-gin about 1 month 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.