action #56651
closed
[functional][u][sporadic] test fails in vim - yast2-booloader left visual artifact
Added by SLindoMansilla over 4 years ago.
Updated about 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Description
Observation¶
yast2-booloader left visual artifact.
Suggestion¶
- Could a
clear/ctrl+l be 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¶
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
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 28
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Status changed from In Progress to Resolved
Doesn't seem to happen anymore.
- Status changed from Resolved to Workable
- 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
I suggest to simply clear the console in the predecessor module yast2_bootloader
What is the status here? We are almost at GMC? Can we get that fixed?
- Priority changed from High to Urgent
- 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.
- 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.
- Status changed from Feedback to Blocked
I have changed the references in openQA to use the bug.
Can you provide here the verification run of the soft-fail in OSD? We can resolve this ticket with it.
- Has duplicate action #57092: [sle][functional][u] test fails in vim - vim-showing-passwd not matched added
- Related to action #58586: [functional][u] test fails in yast2_bootloader - wrong assert_screen and timeout too small for aarch64 added
- Target version changed from Milestone 28 to Milestone 30
let's discuss offline next week
@dheidler could you please check occurences and use of soft-fail needle
- Status changed from Blocked to Resolved
- Related to action #95724: [qe-core] move vim out of installation tests added
Also available in: Atom
PDF