Project

General

Profile

action #56651

[functional][u][sporadic] test fails in vim - yast2-booloader left visual artifact

Added by SLindoMansilla about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2019-09-09
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

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


Related issues

Related to openQA Tests - action #58586: [functional][u] test fails in yast2_bootloader - wrong assert_screen and timeout too small for aarch64Resolved2019-10-23

Related to openQA Tests - action #95724: [qe-core] move vim out of installation testsResolved

Has duplicate openQA Tests - action #57092: [sle][functional][u] test fails in vim - vim-showing-passwd not matchedRejected2019-09-19

History

#1 Updated by okurz about 3 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

#2 Updated by SLindoMansilla about 3 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Target version set to Milestone 28
  • Estimated time set to 42.00 h

#3 Updated by dheidler about 3 years ago

  • Assignee set to dheidler

#4 Updated by dheidler about 3 years ago

  • Status changed from Workable to In Progress

#5 Updated by dheidler about 3 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

#6 Updated by dheidler about 3 years ago

  • Status changed from In Progress to Resolved

Doesn't seem to happen anymore.

#7 Updated by okurz about 3 years ago

  • Status changed from Resolved to Workable

#8 Updated by okurz about 3 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

#9 Updated by okurz about 3 years ago

I suggest to simply clear the console in the predecessor module yast2_bootloader

#11 Updated by maritawerner about 3 years ago

What is the status here? We are almost at GMC? Can we get that fixed?

#12 Updated by SLindoMansilla about 3 years ago

  • Priority changed from High to Urgent

#13 Updated by dheidler about 3 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

#14 Updated by dheidler about 3 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.

#16 Updated by dheidler about 3 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.

#17 Updated by dheidler about 3 years ago

  • Status changed from Feedback to Blocked

#18 Updated by SLindoMansilla about 3 years ago

I have changed the references in openQA to use the bug.

#19 Updated by SLindoMansilla about 3 years ago

Can you provide here the verification run of the soft-fail in OSD? We can resolve this ticket with it.

#21 Updated by SLindoMansilla about 3 years ago

  • Has duplicate action #57092: [sle][functional][u] test fails in vim - vim-showing-passwd not matched added

#22 Updated by okurz about 3 years ago

  • Related to action #58586: [functional][u] test fails in yast2_bootloader - wrong assert_screen and timeout too small for aarch64 added

#23 Updated by mgriessmeier almost 3 years ago

  • Target version changed from Milestone 28 to Milestone 30

let's discuss offline next week

#24 Updated by mgriessmeier almost 3 years ago

dheidler could you please check occurences and use of soft-fail needle

#25 Updated by dheidler almost 3 years ago

It didn't happen in SLE15SP2 yet: https://openqa.suse.de/tests/3722585#step/vim/3

#26 Updated by SLindoMansilla almost 3 years ago

  • Status changed from Blocked to Resolved

#27 Updated by szarate over 1 year ago

  • Related to action #95724: [qe-core] move vim out of installation tests added

Also available in: Atom PDF