coordination #106922
open
coordination #58184: [saga][epic][use case] full version control awareness within openQA
[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 by livdywan about 2 years ago.
Updated 8 months ago.
Category:
Feature requests
Description
Observation¶
https://openqa.opensuse.org/tests/2191509#step/dashboard/4
Suggestions¶
- This appears to be a sporadic issue due to unreliable checks for the un/locked state of the desktop
- Re-consider why we have a copy of these tests in distri-opensuse, or how one inherits the other
- Lead a conversation about how to maintain this
- Copied from action #106919: openqa_install+publish fails in start_test size:M added
- Priority changed from Normal to Urgent
- Target version set to Ready
Please add such CI regressions immediately to our backlog especially when not fixing such issues would mean repeatedly receiving reminder emails.
- Description updated (diff)
- Tracker changed from action to coordination
- Project changed from openQA Infrastructure to openQA Project
- Subject changed from openqa_from_git fails in dashboard to [epic][sporadic] openqa_from_git fails in dashboard due to ensure_unlocked_desktop not expecting password entry screen in case of locked desktop
- Category set to Feature requests
- Status changed from New to Workable
- Priority changed from Urgent to High
Something to follow up with in a mob session as we agreed that the topic in general is something that we all should learn more about. The problem is related to the helper function lib::utils::ensure_unlocked_desktop which we also have in os-autoinst-distri-opensuse. We want to keep os-autoinst-distri-openQA as separate distribution so that we have a good showcase of a realistic openQA test distribution that we as SUSE QE Tools care about ourselves without being as simple as a plain "example" test distribution and also not as complicated or "monolithic" as os-autoinst-distri-opensuse. We should look for a way to better share code among test distributions, e.g. could be git submodules, git subrepos, perl helper packages, etc.
- Parent task set to #80142
- Related to coordination #103122: [epic] Test distribution template for openQA tests to use, e.g. for automatic PR tests in os-autoinst-distri-openQA added
- Related to action #92092: containers: openQA test eventually fails because of timeouts added
- Related to action #44441: test fails in dashboard of openQA-in-openQA test, timeout looking for desktop runner is too short, do we have old x11_start_program code in os-autoinst-distri-openQA? added
- Related to action #46589: [qe-core][functional] Create separate git project for common GNU/Linux functionality added
- Related to action #64078: [openqa-in-openqa] Tests covering bootstrap method added
- Copied to coordination #108527: [epic] os-autoinst wheels for scalable code reuse of helper functions and segmented test distributions added
- Status changed from Workable to Blocked
- Assignee set to okurz
- Priority changed from High to Normal
- Subject changed from [epic][sporadic] openqa_from_git fails in dashboard due to ensure_unlocked_desktop not expecting password entry screen in case of locked desktop to [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
- Parent task changed from #80142 to #58184
- Related to action #133301: quick-fix for openQA-in-openQA lockscreen race condition added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: openqa_from_git
https://openqa.opensuse.org/tests/3522444#step/dashboard/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
- Related to action #135143: [tools] test fails in openqa_from_git -> dashboard size:M auto_review:"no candidate needle.*boot-menu, openqa-desktop":retry added
- Target version changed from Ready to Tools - Next
Also available in: Atom
PDF