Actions
action #61659
closed[functional][u] test fails in yast2_snapper - accessibility bus: connection refused
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-12-23
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
Some errors appears in the console that causes the needle to not match.
Tasks¶
- Investigate and report the product bug that causes those messages.
- Create a workaround needle to continue the test.
Reproducible¶
- In scenario sle-15-SP2-Online-s390x-gnome@s390x-kvm-sle15
- Fails since Build 108.1: https://openqa.suse.de/tests/3727161/modules/yast2_snapper/steps/61
Expected result¶
Last good from sle-15-SP2-Online-x86_64-Build108.1-gnome@64bit: https://openqa.suse.de/tests/3715956
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 4 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: gnome@s390x-kvm-sle15
https://openqa.suse.de/tests/3727161
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"
- The label in the openQA scenario is removed
Updated by mgriessmeier over 4 years ago
- Status changed from New to Rejected
agreed with rodion that [y] team will take over - so closing this as duplicate of #61871
Actions