action #90008
closed[qe-core][typing] test fails in ncurses with typing issues - Improve by using serial_terminal and executing tests via bash
100%
Updated by openqa_review 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: minimal_x
https://openqa.suse.de/tests/5669331
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by tjyrinki_suse about 3 years ago
- Status changed from Workable to Feedback
- Start date deleted (
2021-03-12)
This needs refining of the description.
Updated by szarate about 3 years ago
- Subject changed from [qe-core] test fails with typing issues - Improve by using serial_terminal to [qe-core] test fails in ncurses with typing issues - Improve by using serial_terminal
- Status changed from Feedback to New
I'm starting to believe that anything that has to do with aarch64 in terms of calling things like zypper_call, to be shifted to serial terminal.
However the ncurses tests could be executed with a bash script since they rely on the assert_screen calls...
So:
1- switch to the serial terminal
2- install required packages
3- switch back to root console
4- rewrite test to call bash scripts from data directory rather than typing (prepare_test_data uncompresses everything in /home/bernhard)
5- Profit: make zypper_call switch to serial terminal regardless of the architecture unless no_console_switch=1 (new parameter)
Updated by tjyrinki_suse almost 3 years ago
- Subject changed from [qe-core] test fails in ncurses with typing issues - Improve by using serial_terminal to [qe-core][typing] test fails in ncurses with typing issues - Improve by using serial_terminal
Updated by tjyrinki_suse almost 3 years ago
- Related to coordination #43889: [qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakes added
Updated by tjyrinki_suse almost 3 years ago
- Subject changed from [qe-core][typing] test fails in ncurses with typing issues - Improve by using serial_terminal to [qe-core][typing] test fails in ncurses with typing issues - Improve by using serial_terminal and executing tests via bash
Updated by mgrifalconi almost 3 years ago
Running some statistical investigation (https://progress.opensuse.org/projects/openqatests/wiki/Wiki#Statistical-investigation) to see if some any issue can be spotted:
for i in {003..100} ; do \
/usr/share/openqa/script/clone_job.pl \
--from https://openqa.suse.de \
--host https://openqa.suse.de \
-v 6357721 \
--skip-chained-deps \
ISO= \
SCHEDULE=tests/boot/boot_to_desktop,tests/console/cleanup_qam_testrepos,tests/console/ncurses \
_SKIP_POST_FAIL_HOOKS=1 \
QAM_TESTREPO_FAIL=purge \
TEST=mgrifalconi-investigation-ncurses-$i \
BUILD=mgrifalconi-investigation-ncurses \
_GROUP="mgrifalconi-investigation-ncurses" \
; done
Using mau-extratest as blueprint to copy, since ncurses is currently tested only on installation test suites, and they take a lot of time.
Observation: Why don't we move out as much as possible tests from installation jobs, to reduce risk of breaking the job and all its dependencies?
Does ncurses in particular need to be tested right after the installation? Can't be moved to mau-extratest?
Results: https://openqa.suse.de/tests/overview?build=mgrifalconi-investigation-ncurses
Updated by mgrifalconi almost 3 years ago
- Status changed from Workable to In Progress
Updated by okurz almost 3 years ago
mgrifalconi wrote:
Observation: Why don't we move out as much as possible tests from installation jobs, to reduce risk of breaking the job and all its dependencies?
Does ncurses in particular need to be tested right after the installation? Can't be moved to mau-extratest?
I think QE-Core already has it on the backlog to move more and more tests into "extratests" which boot from existing disk images rather than doing all the tests within the same installation based scenario. However the approach of loading from images is not implemented. For these cases there can be "directly chained dependencies" to ensure that after an installation on a specific (physical) machine the installed OS is booted and subsequent tests can be executed.
Updated by mgrifalconi almost 3 years ago
We agreed to move such test out of installation jobs to extratests or other jobs that boot from a disk, since there is no reason to run it right after installation.
It seems not possible to run the dialog command as part of a shell script, since it blocks there and the script never ends (waiting for a dialog). Considering it's only 2 commands, I propose to skip the switch to bash.
About changing the logic of zypper_call, wouldn't make sense to have a separate progress issue and try to advertise it a bit since everyone is using such method?
Updated by mgrifalconi almost 3 years ago
Created https://progress.opensuse.org/issues/95362 about zypper_call refactoring
Created https://progress.opensuse.org/issues/95365 about moving ncurses out of installation tests
Will not move it to bash script since it's only 2 lines of code to be moved.
Updated by mgrifalconi almost 3 years ago
PR for using serial terminal on zypper_call https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12880
Updated by mgrifalconi almost 3 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Updated by szarate almost 3 years ago
- Related to action #95362: [qe-core] make zypper_call use serial terminal regardless of the architecture added