QA (public) » openQA Project (public) » openQA Tests (public)

I think you can just read the autoinst-log.txt to know which part failed.

From this related issue you'll know what I mean: https://progress.opensuse.org/issues/17872

It really don't have any useful information in log, if it fails in boot part. What we need to do is to let reviewer more easy to tell if it's a fail in our testsuite. If not, the issue will keep bother us a lot in the future. Oliver and Richard also complained this in last week.
https://openqa.suse.de/tests/829634

@yosun any progress here? riafarov has an idea about a PR that he could provide.

@yosun, please take a look on this PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3695

@riafarov, reviewed, and copy some explain of this task here.

Actually the task of split qa_run is for review result more easy, and it's more than just move booting steps out. But you picked the best way to modify it in this PR. Fails before booting success is not failed by what it test, it fails because of OS install or system booting. --> what solved by this PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3695

And fails from booting success to testsuite install finish, is another period not failed by what it test, it fails because of network issue or module issue --> this part I'll do it inside of qa_run.pm

Then fails from testsuite install finish to testsuite start running is because of testsuite internal issue. It means qa_test_* need to be fixed. --> also for me todo in split qa_run.pm

And fails from testsuite run to run finish is what we expected product fail/bug.

yes, we did "our part" so I am fine with removing the tag again although in future we should rather create specific subtickets and resolve them then and not add/remove tags.

I think this task have been finished by Calen, https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4132/files