QA » openQA Project » openQA Tests

PR merged, https://openqa.opensuse.org/tests/634073 triggered to check the screenshots

https://openqa.opensuse.org/tests/634077#step/grub_test/6 shows the situation on openSUSE Tumbleweed, the text is clearly truncated but obviously there is more unused screen space available.

https://openqa.suse.de/tests/1543487 scheduled for SLE15

Actually we are lucky for SLE because it's abbreviated "SLES15" so the whole string matches on the available space: https://openqa.suse.de/tests/1543487#step/grub_test/6

Hm, looking at the latest Tumbleweed test https://openqa.opensuse.org/tests/7088820 I can find that the snapshot names are actually not displayed as screenshots within openQA. It looks like the whole menu of snapshots is not there.

@mloviska I wonder how did you generate the screenshots and why? The screenshots should be recorded by openQA. And just for clarification: The original bug – see the subject line – is not about the timestamps not being visible at all but truncated, i.e. they are not fully visible because they are cut from the right side. This is not a problem for SLE as noted in #33274#note-5 but only for openSUSE.

@okurz, manual test. As long as there is only 1 snapshot, sublist is not displayed.

ah, I see. So even that behaviour changed. https://openqa.opensuse.org/tests/634077#step/grub_test/6 showed the situation – including the bug – from 4 months ago, mentioned in #33274#note-4

We can reproduce the issue on Leap 15.1. Since issue is not touching SLE and TW has changed its behavior, I am not really sure what should be our next step with this ticket.

As recommended in the ticket description I would go for making https://openqa.opensuse.org/tests/715084#step/grub_test/6 a check which we can then soft-fail referencing the bug. It should be enough to have this issue on openSUSE Leap but to further motivate, maybe we can find a SLE product where this happens as well, but just not SLES itself. Maybe "SLES for SAP" is longer?

https://openqa.opensuse.org/tests/717024#step/grub_test/6
@okurz, please review, if you're fine with resolving it.

yes, nice. So my one concern did not turn into reality ;) Please see about the other (two?) points though

I am not really convinced that we are talking about recent builds only, since the behavior changes have been recorded in openQA for few months https://openqa.opensuse.org/tests/677094#step/grub_test/5.
The second point, it would be nice to recognize some string which is enclosed in brackets by a needle. According to the bug, grub can display only limited amount of characters in certain resolution. The same issue was with leap 15.0 GM, thus when this bug is going to be resolved fix, we can just easily remove current workaround.

What workaround do you mean, the record_soft_failure?

Could you please also relate to my comment Nr. 19

okurz wrote:

I really would like to understand better why you urge to keep it closed. Is it OK for you to keep it assigned to myself then until we can clarify how I can improve the description, how another ticket can track it better or what we should do? The bug is important to me and openQA is a very feasible way to show it hence this issue

I guess that's the main issue here, as you have mentioned that it's important for you. I guess we should discuss how far we should get, but I don't believe that bugs get self-resolved, so sending automated 'up' comments do not help here imho. So, let's discuss in more details, as it's a good topic and if we would add soft-failures to all existing bugs then.