QA » openQA Project » openQA Infrastructure

Running the test again doesn't raise the same issue: https://openqa.suse.de/tests/13924015

The empty serial log at the broken test (not even the bootloader messages show up) suggests that the SUT was not powered on.
The additions to the shelly script might make this visible in the future:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19008

dheidler wrote in #note-6:

Running the test again doesn't raise the same issue: https://openqa.suse.de/tests/13924015

The empty serial log at the broken test (not even the bootloader messages show up) suggests that the SUT was not powered on.
The additions to the shelly script might make this visible in the future:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19008

Please remember we can't have an urgent ticket in feedback. You need to confirm that the priority should in fact be lower, or implement mitigations to allow that

Setting due date based on mean cycle time of SUSE QE Tools

I wouldn't run that many jobs as it would wear down the sd cards.

But the working test at https://openqa.suse.de/tests/13924015 shows that is was just a tmp issue.
So I guess we can remove the urgency - especially as the PR making the power cycling more verbose is now merged.

As the PR is not really necessary, I guess we can resolve this one.