action #88283
Updated by JRivrain 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. early. may be related to https://progress.opensuse.org/issues/58670. 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)