mirror of
https://salsa.debian.org/kernel-team/initramfs-tools.git
synced 2026-01-26 15:39:08 +00:00
test: Increase QEMU timeout to 120s
The qemu tests are somehow taking 10 more seconds than usual between
running systemd-udevd and discovering virtio-blk devices, which causes
the qemu-panic-shell test to exceed the timeout and error out:
[ 12.693906] Run /init as init process
Loading, please wait...
Starting systemd-udevd version 256~rc3-2
[ 20.470569] virtio_blk virtio3: 1/0/0 default/read/poll queues
[ 20.715954] virtio_blk virtio3: [vda] 556 512-byte logical blocks (285 kB/278 KiB)
Begin: Loading essential drivers ... [ 22.057615] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input2
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
[...]
qemu-system-amd64: terminating on signal 15 from pid 17745 (timeout)
Increase the timeout to 120s, so the qemu-panic-shell test can continue
long enough to print the emergency shell the test is looking for. S390X
also has a 120s timeout, so fold that into the new default case as well.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
This commit is contained in:
parent
4797c54c5f
commit
03d196f7c6
6
debian/tests/test-common
vendored
6
debian/tests/test-common
vendored
@ -27,12 +27,8 @@ ppc64el)
|
||||
# Slowest execution seen in Ubuntu ppc64el autopkgtest: 230 seconds
|
||||
QEMU_TIMEOUT=600
|
||||
;;
|
||||
s390x)
|
||||
# Slowest execution seen in Ubuntu s390x autopkgtest: 58 seconds
|
||||
QEMU_TIMEOUT=120
|
||||
;;
|
||||
*)
|
||||
QEMU_TIMEOUT=60
|
||||
QEMU_TIMEOUT=120
|
||||
esac
|
||||
|
||||
if [ -n "${AUTOPKGTEST_TMP-}" ]; then
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user