action #42863
closed
[sle][functional][u] test fails in first_boot - hard to see what is exactly the cause for timeout issue
Added by zluo over 5 years ago.
Updated about 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Description
compared with last successful test run, it shows grub menu to boot up, but first boot runs out of time.
It is hard to determine what the real cause for this failure. Checked other logs, no issue found. Maybe we need to increase timeout for wait_boot (aarch64)?
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-aarch64-minimal_x@aarch64 fails in
first_boot
Reproducible¶
Fails since (at least) Build 0435 (current job)
Expected result¶
Last good: 0432 (or more recent)
Further details¶
Always latest result in this scenario: latest
This is not related to bootloader changes for aarch64, the SUT is already booting.
If you check serial0.txt in the end...
[ 0.005048] ITS@0x8080000: Unable to locate ITS domain handle
[ 0.005087] ITS@0x8080000: Unable to locate ITS domain handle
Which could be already a starting point. If you look at the video, it stopped in the same screen for quite some time. and the SUT did not react to the test sending the esc
key, (about 3 mins later)
Seems a bit sporadic, I would suggest to run the same scenario 100 times with memory dumps enabled... so that a developer could look at it, if it happens again...
All the three last mentioned jobs seem to show the same problem but different to the original one: The getty login prompt shows up on the serial device (multiple times) so I suspect it's a different issue.
Very likely the abi break of mozjs60, that I 'cured' in openSUSE:Factory by rebuilding everything aginst mozjs60
Just executed, for ARM and PowerPC:
for ARCH in ARM PowerPC; do
for pkg in $(dependson mozjs60); do
osc rebuildpac openSUSE:Factory:${ARCH} $pkg -r standard;
done;
done
both archs should thus have gnome-shell (and other consumers) rebuilt against mozjs60 with the new ABI
(I just triggered the same for libzypp, which also had an ABI break)
- Priority changed from Normal to High
- Target version set to Milestone 21
yes, that looks more like it
@pvorel I think this is neither #42863, this ticket, nor #31375, rather its own, new thing. The 'ret' key in the grub screen does not have an effect. Better track as its own issue.
- Related to action #42038: [sle][functional[u] test fails in shutdown - add post_fail_hook for shutdown module if possible added
- Related to action #43064: [functional][u] test fails in boot_into_snapshot and reboot_gnome with encrypted setup - test not waiting long enough for shutdown/reboot until we end up in grub which shows in post_fail_hook added
- Blocked by action #32683: [sle][functional][u][medium] Implement proper post_fail_hook for boot_to_desktop added
- Status changed from New to Blocked
- Assignee set to okurz
- Blocks action #35892: [qe-core][functional][hard] test fails in kdump_and_crash - improve bootup/shutdown debugging approach added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: minimal_x+uefi
https://openqa.suse.de/tests/2326139
- Target version changed from Milestone 21 to Milestone 22
- Target version changed from Milestone 22 to Milestone 23
- Status changed from Blocked to Resolved
Also available in: Atom
PDF