action #88283
Updated by riafarov over 3 years ago
## Observation
We can see in the console0.txt file and on screen that the proper string was written, but it looks like the console output was somehow caught too early:[Here](https://openqa.suse.de/tests/5347948#step/bootloader_start/8) we can see the incomplete string. may be related to https://progress.opensuse.org/issues/58670.
```
# wait_serial expected: qr/command line:.*/msi
# Result:
[ 0.000000] Linux version 5.3.18-44-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Tue Jan 19 15:02:32 UTC 2021 (90d282a)
[ 0.000000] Command line: initrd=initrd splash=silent Y2DEBUG=1 vga=791 video=1024x768 plymouth.ignore-serial-consoles console=ttyS0 console=tty linuxrc.log=/dev/ttyS0 linuxrc.core=/dev/ttyS0 linuxrc.debug=4,trace startshell=1 YUI_HTTP_PORT=39097 YUI_HTTP_REMOTE=1 YUI_REUSE_PORT=1 reboot_timeout=0 kernel.softlockup_panic=1 regurl=http://all-133.1.proxy.
```
So we can improve regexp so that we fully capture wait serial, e.g. by waiting for the next line starting with `[`
openQA test in scenario sle-15-SP3-Full-x86_64-detect_yast2_failures@64bit fails in
[bootloader_start](https://openqa.suse.de/tests/5347948/modules/bootloader_start/steps/9)
## Test suite description
Specific test displaying as much dialogs as possible to increase test coverage, which would fail hard in case any yast2 failure is found in logs.
## Reproducible
Fails since (at least) Build [109.1](https://openqa.suse.de/tests/5188766)
## Expected result
Last good: [100.1](https://openqa.suse.de/tests/5150803) (or more recent)
## Further details
Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Full&machine=64bit&test=detect_yast2_failures&version=15-SP3)