action #42830
closed
[functional][u] test fails in kontact - akregator was launched at the first place
Added by mlin7442 over 5 years ago.
Updated over 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 21
Description
Observation¶
openQA test in scenario opensuse-15.1-DVD-x86_64-kde-wayland@64bit_virtio-2G fails in
kontact
maybe wrong typed or krunner issue, Akregator was launched at the first place, and krunner screen wrongly matched https://openqa.opensuse.org/tests/780545#step/kontact/3
Reproducible¶
Fails since (at least) Build 319.3
Expected result¶
Last good: 319.2 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Subject changed from test fails in kontact - akregator was launched at the first place to [functional][u] test fails in kontact - akregator was launched at the first place
- Target version set to Milestone 21
- Is duplicate of action #35589: [functional][u][opensuse][sporadic][medium] test fails in kontact - needs workaround for boo#1105207, then akregator not closed added
- Status changed from New to Rejected
- Assignee set to okurz
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: kde-wayland@64bit_virtio-2G
https://openqa.opensuse.org/tests/802630
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: kde-wayland@64bit_virtio-2G
https://openqa.opensuse.org/tests/813010
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: kde-wayland@64bit_virtio-2G
https://openqa.opensuse.org/tests/825691
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: kde-wayland@64bit_virtio-2G
https://openqa.opensuse.org/tests/837195
Also available in: Atom
PDF