Pressing a key does not interrupt the boot sequence after rainbow" splash screen

[Dominik Viererbe]

I tested the following image on the Raspberry Pi 3B+:
http://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/20230217.1/jammy-preinstalled-server-arm64+raspi.img.xz

Testcase (https://iso.qa.ubuntu.com/qatracker/milestones/442/builds/271829/testcases/1721/results):
1. Immediately after the "rainbow" splash screen, U-Boot starts. Press a key
to interrupt the sequence, then type "boot" to continue it.
    Check that the U-Boot prompt (including a two-second wait) appears on
    the primary monitor connected to the Pi, that the keyboard will interrupt
    the sequence, and that boot successfully concludes after resumption.
2. During the boot sequence, U-Boot starts interacting via serial (GPIO14
and GPIO15, pins 8 and 10 respectively, on the 40-pin GPIO header). Press
a key to interrupt the sequence, then type "boot" to continue it.
    Check that the U-Boot prompt (including a two-second wait) appears on
    the attached serial console, that the keyboard will interrupt
    the sequence, and that boot successfully concludes after resumption.

The boot sequence waited for 2 seconds, but was not interrupted by any keypress on the keyboard. I tested this multiple times.

I attached the serial output of the boot sequence.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2008244

[Dave Jones (waveform)]

I'm afraid this is another of the "confusing" tests. This one only applies to those Ubuntu images that use u-boot on the Pi, which is all images from focal and before. From groovy onwards we stripped out u-boot and use the pi's bootloader only (which cannot be interrupted in this fashion). Unfortunately the test case generator doesn't know anything about release-specific output, so this case appears in all generated tests whether for focal or jammy but it should be ignored when dealing with jammy.

I'll try and find a way to fix this ... when I understand how https://git.launchpad.net/ubuntu-manual-tests?h=main maps to the ISO tracker website!