QA » openQA Project » openQA Tests

We can see that the plymouth boot splash is still active and the balls are running left and right :) The generic post-fail-hook from https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/opensusebasetest.pm#L628 seems to trigger the detection of blocked tasks where there are none but probably https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/opensusebasetest.pm#L645 is never reached because the variable "in_boot_desktop" is not set. I recommend to look into how the variable should be set when a boot is requested from grub_test_snapshot so that a more helpful post_fail_hook content is executed, for example also https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/opensusebasetest.pm#L650 should help if it would be called.

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: offline_sles12sp3_scc_base_all_full
https://openqa.suse.de/tests/2396588

latest result show can not reach grub_test_snapshot.
https://openqa.suse.de/tests/2448879

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: offline_sles12sp4_pscc_sdk_def_full
https://openqa.suse.de/tests/2511585

Any update here? This blocking quite some testcases and we need to have everything in shape soon. We are approaching RC2.

Ok, can we add a softfail to those testcases? We are almost at RC2 and we need a clear product status in openQA?

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: offline_sles12sp3_rmt_sdk_all_full
https://openqa.suse.de/tests/2741519