action #56651
closed[functional][u][sporadic] test fails in vim - yast2-booloader left visual artifact
0%
Description
Observation¶
yast2-booloader left visual artifact.
Suggestion¶
- Could a
clear/ctrl+lbe enough to redraw the screen before executing vim?
Tasks¶
- File a product bug for Yast, because it is leaving visual artifacts on the console.
- Create a workaround needle in module yast2_booloader to detect the bug.
- Create a workaround needle in module vim to make it continue testing
- Maybe vim could be started without syntax highlighting to avoid the problem of colors.
Reproducible¶
- In scenario sle-12-SP5-Server-DVD-aarch64-system_performance@aarch64
- Fails since Build 0307
- Example of build 0307
Expected result¶
Last good: 0303
Further details¶
- Always latest result in this scenario: latest
- https://en.wikipedia.org/wiki/Visual_artifact
Updated by okurz about 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: textmode
https://openqa.suse.de/tests/3397794
Updated by SLindoMansilla about 5 years ago
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 28
- Estimated time set to 42.00 h
Updated by dheidler about 5 years ago
- Status changed from Workable to In Progress
Updated by dheidler about 5 years ago
This didn't happen anymore for two weeks.
On current builds it seems to work fine: https://openqa.suse.de/tests/3448410
Running 100 jobs for verification: https://openqa.suse.de/tests/overview?distri=sle&build=0346%3Apoo56651&version=12-SP5
Updated by dheidler about 5 years ago
- Status changed from In Progress to Resolved
Doesn't seem to happen anymore.
Updated by okurz about 5 years ago
- Status changed from Resolved to Workable
happened again: https://openqa.suse.de/tests/3469943#step/vim/4
Updated by okurz about 5 years ago
- Subject changed from [functional][u] test fails in vim - yast2-booloader left visual artifact to [functional][u][sporadic] test fails in vim - yast2-booloader left visual artifact
Updated by okurz about 5 years ago
I suggest to simply clear the console in the predecessor module yast2_bootloader
Updated by dheidler about 5 years ago
This is already done: https://openqa.suse.de/tests/3469943#step/yast2_bootloader/9
Updated by maritawerner about 5 years ago
What is the status here? We are almost at GMC? Can we get that fixed?
Updated by SLindoMansilla about 5 years ago
- Priority changed from High to Urgent
Updated by dheidler about 5 years ago
So ncurses applications like yast or vim usually don't write to the normal terminal scrollback buffer to prevent polluting it but use the "alternative screen".
My last idea is to explicitly run the clear command on the alternative screen:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8716
100 jobs with that PR:
https://openqa.suse.de/tests/overview?version=12-SP5&distri=sle&build=0363%3Apoo56651
Updated by dheidler about 5 years ago
- Status changed from Workable to In Progress
The question is if this is a product bug.
I will just create a bug to be sure - devs can still close it.
Anyway this should not really harm GMC testing as we can simply restart jobs with this problem as this is very sporadic.
Updated by dheidler about 5 years ago
Updated by dheidler about 5 years ago
- Status changed from In Progress to Feedback
- Priority changed from Urgent to High
Created a workaround needle and will handle this as a product bug for now.
Updated by SLindoMansilla about 5 years ago
I have changed the references in openQA to use the bug.
Updated by SLindoMansilla about 5 years ago
Can you provide here the verification run of the soft-fail in OSD? We can resolve this ticket with it.
Updated by dheidler about 5 years ago
Let's see if we will run into the issue: https://openqa.suse.de/tests/overview?version=12-SP5&groupid=139&distri=sle&build=0363%3Apoo56651_wo
Updated by SLindoMansilla about 5 years ago
- Has duplicate action #57092: [sle][functional][u] test fails in vim - vim-showing-passwd not matched added
Updated by okurz about 5 years ago
- Related to action #58586: [functional][u] test fails in yast2_bootloader - wrong assert_screen and timeout too small for aarch64 added
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 28 to Milestone 30
let's discuss offline next week
Updated by mgriessmeier almost 5 years ago
@dheidler could you please check occurences and use of soft-fail needle
Updated by dheidler almost 5 years ago
It didn't happen in SLE15SP2 yet: https://openqa.suse.de/tests/3722585#step/vim/3
Updated by SLindoMansilla over 4 years ago
- Status changed from Blocked to Resolved
Updated by szarate over 3 years ago
- Related to action #95724: [qe-core] move vim out of installation tests added