action #135143
closed
[tools] test fails in openqa_from_git -> dashboard size:M auto_review:"no candidate needle.*boot-menu, openqa-desktop":retry
Added by osukup over 1 year ago.
Updated about 1 year ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_from_git@64bit-2G fails in
dashboard
Test suite description¶
test fails in ensure_unlocked_desktop .. send first click in login screen to show password prompt but not type password.
I tried create needle -> needle correctly saved, but it looks like ensure_unlocked_desktop has problem in main loop :(
Reproducible¶
Fails since (at least) Build :TW.22712
Expected result¶
Last good: :TW.22711 (or more recent)
Further details¶
Always latest result in this scenario: latest
Acceptance criteria¶
AC1: test successfully unlocks desktop
- Related to coordination #106922: [epic][sporadic] openqa_from_git fails in dashboard due to ensure_unlocked_desktop not expecting password entry screen in case of locked desktop auto_review:"match=desktop-runner,screenlock timed out.*":retry added
- Target version set to Ready
- Subject changed from [tools] test fails in openqa_from_git -> dashboard to [tools] test fails in openqa_from_git -> dashboard size:M
- Status changed from New to Workable
looks like main problem are wrongly tagged needles ..
- Status changed from Workable to In Progress
- Due date set to 2023-09-27
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Resolved
changes merged. So now ensure_unlocked_desktop should work as excepted
- Status changed from Resolved to Workable
- Assignee deleted (
osukup)
- Priority changed from Normal to Urgent
- Subject changed from [tools] test fails in openqa_from_git -> dashboard size:M to [tools] test fails in openqa_from_git -> dashboard size:M auto_review:"no candidate needle.*boot-menu, openqa-desktop":retry
- Priority changed from Urgent to Normal
- Due date deleted (
2023-09-27)
- Target version changed from Ready to Tools - Next
- Target version changed from Tools - Next to Ready
- Assignee set to jbaier_cz
- Related to action #126680: [openQA-in-openQA] no candidate needle with tag(s) 'boot-menu, openqa-desktop' matched in worker size:M added
- Status changed from Workable to In Progress
Will try to replicate the issue; this might be also already resolved or/and it might be also mitigated with #126680
- Status changed from In Progress to Feedback
After looking at the code, I think the issue is (as hinted above) that generic-desktop and screenlock shouldn't be on used on the same needle. The code expects generic-desktop to be the unlocked, usable, target screen. https://github.com/os-autoinst/os-autoinst-needles-openQA/pull/23 should make the situation right for cases, where the installation is long enough for the screen to be locked.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF