action #106535
Updated by tjyrinki_suse about 2 years ago
## Observation ### Hypotesis Here I believe that the cause is the root console being used to print all of the output, and the screen taking long time to print all that output, switching to serial console should fix that. As a suggestion altering save_and_upload_logs to directly print the logs to a file, instead of printing to the console should improve the log collection overall for the whole project. openQA test in scenario sle-15-Server-DVD-Incidents-x86_64-systemd_sapstart_check@64bit fails in [systemd_sapstart_check](https://openqa.suse.de/tests/8121448/modules/systemd_sapstart_check/steps/30) ## Test suite description systemd/sapstart compatibility check ## Reproducible Fails since (at least) Build [:22724:zypper](https://openqa.suse.de/tests/8121448) (current job) ## Expected result Last good: [:22622:perl-Net-SNMP](https://openqa.suse.de/tests/8117541) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-Incidents&machine=64bit&test=systemd_sapstart_check&version=15) ## Acceptance Criteria AC1: Switch the test from root console to serial console AC2: Based on how well it works after that, give an opinion whether additional ticket should be created to modify save_and_upload_logs to print logs directly to a file