action #62624
closed
[functional][y] Test if workaround for bsc#1041747 can be disabled
Added by riafarov over 4 years ago.
Updated over 4 years ago.
Target version:
SUSE QA - Milestone 31
Description
Motivation¶
We would like to test our product in the setup which is closer to the customer setups. Workaround for bsc#1041747 is to use single thread and single core.
We want to check if setup is stable enough to use it.
- Status changed from In Progress to Resolved
Resolving, as we cannot remove the workaround. However, now issue is not with mistyping, but with meta-keys (alt, shift, etc.), so VNC_TYPING_LIMIT might help.
There is also the possibility to select a different typing speed selectively, e.g. for the single line of code where typing fails. VNC_TYPING_LIMIT applies to the global test execution so that would slow down the tests potentially significantly but bsc#1041747 is really limited to "user_settings".
okurz wrote:
There is also the possibility to select a different typing speed selectively, e.g. for the single line of code where typing fails. VNC_TYPING_LIMIT applies to the global test execution so that would slow down the tests potentially significantly but bsc#1041747 is really limited to "user_settings".
On ppc we have seen these issues not only in that module, but also in bootloader. Actually, it's also visible with single thread and single CPU. As current plan is to drop power kvm, we are not considering to invest more time in it. However, scenarios which must be executed on multi threaded env, are already scheduled on those workers. So, based on this knowledge, we will keep things as they are. Jose is updated on this, so coverage for kernel tests will be adjusted accordingly if needed.
Also available in: Atom
PDF