action #20332
closed[opensuse][functional] test fails in yast2_datetime
0%
Description
Observation¶
Not sure if this is a product bug or caused by a previous test. Please check and file bug if it's a bug in yast.
openQA test in scenario opensuse-42.3-DVD-x86_64-yast2_ui@64bit fails in
yast2_datetime
Reproducible¶
Fails since (at least) Build 0229
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 7 years ago
- Blocks action #19922: [sle][functional][opensuse]Harmonize extratests/yast2_ui tests for openSUSE and SLE added
Updated by zluo almost 7 years ago
- Status changed from New to Feedback
- Priority changed from Normal to Low
checked the latest job, no issue at all:
https://openqa.opensuse.org/tests/latest?flavor=DVD&distri=opensuse&machine=64bit&version=42.3&test=yast2_ui&arch=x86_64#step/yast2_datetime/10
checked history for test results in last 2 month, only one time failed. I don't think this is an issue which requires any action from my side.
Updated by riafarov almost 7 years ago
- Status changed from Feedback to In Progress
- Assignee changed from zluo to riafarov
Test still fails on leap, I'll take care of it.
Updated by riafarov almost 7 years ago
- Status changed from In Progress to Feedback
- Assignee changed from riafarov to okurz
Problem was that pop-up needle was removed from repo. I have reintroduced it here: https://github.com/os-autoinst/os-autoinst-needles-opensuse/commit/d980b00c692c62647553582eb1392a04052d8820
Underlying issue is that this popup is not always there, so it may happen that it's not used for 2 weeks, especially if there are no triggers for the job.
@okurz: Please, either resolve the issue, or let me know if we want to do any extra activities here.
Updated by riafarov almost 7 years ago
- Subject changed from test fails in yast2_datetime to [opensuse][functional] test fails in yast2_datetime
Updated by okurz almost 7 years ago
- Status changed from Feedback to Resolved
I guess we are good here. Most likely we will just have to revisit when the next leap version will be developed.