action #14826
closed[tool]test fails on selecting consoles
100%
Description
Observation¶
openQA test in scenario sle-12-SP3-Server-DVD-x86_64-migration_zdup_offline_sle12_ga_allpatterns+workaround_deps@64bit fails in
setup_zdup
Reproducible¶
Fails since (at least) Build 0057 (current job)
Expected result¶
Last good: 0057 (or more recent)
Problem¶
H1. we are still in bootup and are switching too fast to text terminal, then DM switches back to focus -> E1
H2. console never shows up
suggestion¶
- E1. reproduce locally and wait a bit before calling
select_console - add logs gathering to
setup_zdupstep
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 7 years ago
- Description updated (diff)
- Assignee set to asmorodskyi
Updated by asmorodskyi over 7 years ago
- Status changed from In Progress to Resolved
- Rerun on same build pass
- run on next build also pass
this push us to idea that it was random false positive which has too low priority so closing
Updated by asmorodskyi over 7 years ago
- Status changed from Resolved to New
- Assignee deleted (
asmorodskyi)
Reopen as issue strike back :
https://openqa.suse.de/tests/636835#step/setup_zdup/5
Updated by okurz over 7 years ago
- Has duplicate action #11514: [ppc64le] ppc64 can't switch to console tty2 in textmode added
Updated by okurz over 7 years ago
- Subject changed from test fails on selecting root console in setup_zdup module to test fails on selecting consoles
https://openqa.suse.de/tests/665359#step/yast2_lan/1 seems to show a similar problem. The command is typed shortly after select_console 'user-console' in yast2_lan.pm and therefore part of the command is lost.
Two suggestions, either
explicitly check with assert_screen that the clean prompt shows up
orjust wait_screen_change
wait_still_screen is not a good idea, as the blinking cursor would never resemble a "still" image
Updated by okurz over 7 years ago
- Has duplicate action #13460: Unexpected "(" before expected type_string content added
Updated by okurz about 7 years ago
- Target version set to Milestone 5
recent example: https://openqa.suse.de/tests/758690#step/ssh_cleanup/1
Updated by okurz about 7 years ago
- Target version changed from Milestone 5 to Milestone 6
Updated by okurz about 7 years ago
recent example: glibc_i686 (http://openqa.suse.de/t789876)
Updated by okurz about 7 years ago
Updated by okurz about 7 years ago
- Status changed from New to In Progress
- Assignee set to okurz
looking to define a needle which can be unambiguous and differentiate between user-console and root-console. Something like the text-logged-in-root but for cleared console.
Updated by RBrownSUSE about 7 years ago
- Subject changed from test fails on selecting consoles to [tool]test fails on selecting consoles
Flagging as [tools] just so I remember to keep an eye on this ticket
Updated by okurz about 7 years ago
https://github.com/os-autoinst/os-autoinst/pull/738 and https://github.com/os-autoinst/os-autoinst/pull/740 for corresponding os-autoinst changes, both merged.
Now needs to be deployed.
then https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/334 and https://github.com/os-autoinst/os-autoinst-needles-opensuse/pull/173, then tests https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2571
Updated by okurz about 7 years ago
os-autoinst deployed, tests and needles deployed
Updated by okurz about 7 years ago
first job passed on osd as proof-run: https://openqa.suse.de/tests/830142#step/logpackages/9
but some failed already, e.g. https://openqa.suse.de/tests/830073#step/glibc_i686/6 . but this one turned out to be started already in before it seems.
Will fix and monitor
Updated by okurz about 7 years ago
- Status changed from In Progress to Resolved
not seen anymore recently. assumed to be fixed.