action #77935
closed
[qe-core][opensuse][s390x] cursor in console test 'ncurses-simple-dialog' as a result of a failed needle - cursor should be hidden (moved to corner)
Added by AdaLovelace over 3 years ago.
Updated over 3 years ago.
Category:
Bugs in existing tests
Description
Observation¶
Packages dialog and libdialog are installed successfully.
The test ncurses fails because of a cursor in the needle 'ncurses-simple-dialog'. The needle can not match then
The openQA test in scenario opensuse-Tumbleweed-DVD-s390x-textmode@s390x-zVM-vswitch-l2 fails in
ncurses
Test suite description¶
Maintainer: okurz
Installation in textmode and selecting the textmode "desktop" during installation.
Reproducible¶
Fails since (at least) Build 20201110
Expected result¶
The test should accept the needle 'ncurses-simple-dialog'.
The cursor should not be required.
Further details¶
Always latest result in this scenario: latest
Files
The cursor likely comes from the Xvnc client used in the a bit complicated s390x backend (which I demonstrated to you another time). So unlike on qemu where we have the ncurses dialog in a true tty here we have "xterm-console" in full screen within Xvnc connected over VNC+ssh to the z/VM instance. Hence the cursor. This is a bit unfortunate and there is a command to move the mouse cursor to a separate position. This should be done on s390x as a better workaround. However what I have done now is create a simple updated needle masking the cursor, see screenshot:
You have all the necessary permissions to create needles yourself but within os-autoinst-distri-opensuse this requires quite some expertise so I understand that you don't want to take this too easy :) The documentation, guides and videos on http://open.qa/ can provide a good start.
Actually, as the last snapshot of Tumbleweed s390x according to https://factory-dashboard.opensuse.org/ 20200413 and considering that now the test passed way beyond the installation and initial bootup and even initial console tests showed up fine I would just mark the ticket as non-blocking for release and accept that all the later test modules are not tested. This can be done by adding the comment @ttm ignore whenever ttm mentions this ticket as unknown issue. This can be written in the very same ticket reference comment in a new line or a separate comment.
I did that now but likely the second test scenario in the build is still blocking release.
I have added the subject keyword "[qe-core]" to mark this ticket as being in the responsibility area of the team "SUSE QE Core" to the best of my knowledge.
I wasn't sure whether a new needle with the cursor would be a good choice because I thought that the cursor could have different positions and then the needle would not match again.
I didn't know about that:
This is a bit unfortunate, and there is a command to move the mouse cursor to a separate position.
That makes a choice between solutions easier.
- Status changed from New to Workable
(don't mind me mass editing tickets, thank you for working on this one)
- Status changed from Workable to Resolved
It seems that it is fixed.
Thank you!
Also available in: Atom
PDF