action #33256
closed[sle 12 sp4][functional][y][yast][fast] test fails in keymap_or_locale - us_keymap_logged_x11 doesn't match or is missing
0%
Description
Updated by okurz almost 7 years ago
- Subject changed from [sle 12 sp4[[functional] test fails in keymap_or_locale - us_keymap_logged_x11 doesn't match or is missing to [sle 12 sp4[[functional][y][yast][fast] test fails in keymap_or_locale - us_keymap_logged_x11 doesn't match or is missing
- Due date set to 2018-03-27
- Assignee set to mloviska
- Priority changed from Normal to Urgent
- Target version set to Milestone 15
As we mentioned we want to prioritize the work on recent failures so please tag and prioritize accordingly.
Updated by mloviska almost 7 years ago
Updated by okurz almost 7 years ago
- Related to action #33247: [sle][functional][u][s390x][medium] test fails in keymap_or_locale - missing select root console added
Updated by okurz almost 7 years ago
https://openqa.opensuse.org/tests/634019#step/keymap_or_locale/9 is an example of the keymap_or_locale module running before consoletest_setup and this can cause multiple problems. As we have seen with the test failures in the past two days the keymap check needles very much rely on the correct console font being used which is only ensured by consoletest_setup. I suggest to rethink where we can execute the keymap_or_locale step. IMHO it should really come behind consoletest_setup. Can you try that please?
Updated by mloviska almost 7 years ago
Sure, I can try to reschedule the test after consoletest_setup. I am wondering whether it would not cause a problem when keymap test should be executed in any window manager.
In this particular case that you have pointed, I cannot see any font change. But maybe it is just really minor difference which I have problems to distinguish.:) https://openqa.opensuse.org/tests/634019#step/keymap_or_locale/9
Updated by riafarov almost 7 years ago
- Subject changed from [sle 12 sp4[[functional][y][yast][fast] test fails in keymap_or_locale - us_keymap_logged_x11 doesn't match or is missing to [sle 12 sp4][functional][y][yast][fast] test fails in keymap_or_locale - us_keymap_logged_x11 doesn't match or is missing
- Status changed from New to Workable
Updated by mloviska almost 7 years ago
Hi Oli, could you please double check these runs ?
https://openqa.suse.de/tests/1545207#step/keymap_or_locale/14
Successful run:
https://openqa.suse.de/tests/1542546
I think that this commit is causing problems whenever we need to match tty for bernhard.
https://gitlab.suse.de/openqa/os-autoinst-needles-sles/commit/29b05a3bd692887c75a846d144121083b08d40a8
Updated by okurz almost 7 years ago
yes, that should be solved by a new needle tty4-selected I just created
Updated by mloviska almost 7 years ago
- Status changed from Workable to In Progress
Updated by mloviska almost 7 years ago
Updated by mloviska almost 7 years ago
local verification run:
sle-12-SP4-Server-DVD-s390x-Build0234-lvm-encrypt-separate-boot@zkvm
Updated by okurz almost 7 years ago
anything else that you see missing? https://openqa.suse.de/tests/1546882 is the last job in the original scenario not failing in the keymap_or_locale module so are we good?
Updated by mloviska almost 7 years ago
We are missing OSD verification run only. I have tried to trigger the job in development group, but it fails on reconnect_s390 module.
Updated by mloviska almost 7 years ago
- Status changed from In Progress to Feedback
Updated by riafarov almost 7 years ago
Looks like this one can be finally resolved? Or are we aware of any issues where we could not get run in production?
Updated by mloviska over 6 years ago
I am testing related issue with https://openqa.suse.de/tests/1561536/modules/keymap_or_locale/steps/3. Where we need to wait for tty3 to be activated. Afterwards we can resolved this ticket as well.
Updated by mloviska over 6 years ago
- Due date changed from 2018-03-27 to 2018-04-10
- Status changed from Resolved to Feedback
Related PR for s390x
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4713
Updated by riafarov over 6 years ago
Hey! Could you please check if it's resolved now? Last run looks good https://openqa.suse.de/tests/1585050 and no new issues in the last 8 days.
Updated by mloviska over 6 years ago
So far it works well. I would suggest to close this ticket. WDYT?
Updated by mloviska over 6 years ago
- Status changed from Feedback to Resolved