action #62783
open
[opensuse] test fails in welcome - seems like a completely different screen is expected (network initialization vs welcome screen)
Added by lkocman about 4 years ago.
Updated about 1 month ago.
Category:
Bugs in existing tests
Description
Observation¶
Seems like a completely different screen is expected (Network initialization vs Welcome screen).
openQA test in scenario opensuse-15.2:S:N-Staging-DVD-x86_64-minimalx@64bit fails in
welcome
Test suite description¶
MAX_JOB_TIME for bypass poo#44408
Reproducible¶
Fails since (at least) Build N.340.1 (current job)
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Not sure if the beta popup dialog doesn't cause the screen block.
- Subject changed from test fails in welcome to test fails in welcome - seems like a completely different screen is expected (network initialization vs welcome screen)
@lkocman I recommend you always update the ticket subject line from the generic "test fails in " with a bit more details. The very generic summaries are not really motivating people to pick up the ticket fast. As in your observation you already stated what is the likely cause why not just add that in the summary :)
As you have access to the SUSE internal teams you can also provide a team tag in the subject line for the team that you think is the best assignee. In this case however I guess the release management team, e.g. you yourself could be best assignee as the failure happens in a new staging project and also is the first test in this scenario. Please also fill the "Expected result" in the ticket.
- Subject changed from test fails in welcome - seems like a completely different screen is expected (network initialization vs welcome screen) to [opensuse] test fails in welcome - seems like a completely different screen is expected (network initialization vs welcome screen)
- Status changed from New to Workable
- Assignee set to lkocman
@lkocman this is in staging. We know that the test module works just fine, probably a submission in the staging project caused this.
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.
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.
Also available in: Atom
PDF