action #66292
closed[functional][y] Investigate yast_keyboard test fail on aarch64, ppc64le
0%
Description
Observation¶
openQA test in scenario sle-15-SP2-Online-aarch64-yast2_cmd@aarch64 fails in
yast_keyboard
The test started failing after https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10102 is introduced.
The PR removed timeout workaround for Sle15-SP2, but it seems like another problem exists on aarch64.
So we have 2 hypothesis, either changes do not get applied immediately or bug is still valid.
Therefore, we should either stabilize test execution or reopen the bug.
The fail in y2logs seems to be due Couldn't open /dev/ttyS0.
2020-04-30 03:51:34 <1> susetest(6287) [Ruby] lib/cheetah.rb:160 Executing "loadkeys -C /dev/ttyS3 -C /dev/ttyS2 -C /dev/ttyS1 -C /dev/ttyS0 us".
2020-04-30 03:51:34 <3> susetest(6287) [Ruby] lib/cheetah.rb:208 Error output: Couldn't open /dev/ttyS0
2020-04-30 03:51:34 <3> susetest(6287) [Ruby] lib/cheetah.rb:180 Status: 1
2020-04-30 03:51:34 <1> susetest(6287) [Ruby] strategies/kb_strategy.rb:63 Execution of "loadkeys -C /dev/ttyS3 -C /dev/ttyS2 -C /dev/ttyS1 -C /dev/ttyS0 us" failed with status 1: Couldn't open /dev/ttyS0.
2020-04-30 03:51:34 <1> susetest(6287) [Ruby] strategies/kb_strategy.rb:64 Error output: Couldn't open /dev/ttyS0
Task¶
- Try to identify if it is a product issue;
- Raise an appropriate ticket;
- Implement workaround if it is applicable (e.g. it seems like the issue should not happen if the timeout will be reverted to the value before the PR was introduced.
Test suite description¶
QAM team has developed some tests using YaST cmd line, which is less costly to execute and maintain. This test suite is using those test modules for QA SLE functional.
Reproducible¶
Fails since (at least) Build 183.5
Expected result¶
Last good: 181.4 (or more recent)
Further details¶
Always latest result in this scenario: latest