coordination #58184: [saga][epic][use case] full version control awareness within openQA, e.g. user forks and branches, fully versioned test schedules and configuration settings
coordination #108527: [epic] os-autoinst wheels for scalable code reuse of helper functions and segmented test distributions
quick-fix for openQA-in-openQA lockscreen race condition
We plan to improve our code with #115019 but sometimes we are still hit by a race condition where the lockscreen is properly handled but the subsequent
assert_screen catches too quickly on the still visible password prompt as in https://openqa.opensuse.org/tests/3451081#step/worker/3. We should try to look for a quick fix to ease our mind.
- AC1: fail ratio below 1%
- Try to fix the test
- Run statistical investigation before+after
- 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
- Parent task set to #108527
Well, it is related to our ideas about "wheels" because what I am changing would need to end up in a wheels repo for a "ensure_unlocked_desktop" helper as well. And also the parent task is still our motivation for the work on this although the trigger for today was the recent CI test failures.
end=100 openqa-clone-set https://openqa.opensuse.org/tests/3451193
- Status changed from In Progress to Resolved
https://openqa.opensuse.org/tests/overview?distri=openqa&version=Tumbleweed&build=okurz_investigation shows 0/100 failures so a fail ratio of 0±0% with computed failure probability < 3.00%