amd64 autopkgtests regressed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Kinetic |
Won't Fix
|
High
|
Unassigned | ||
Lunar |
Won't Fix
|
High
|
Unassigned |
Bug Description
In mid-September of 2022 the amd64 autopkgtest for livecd-rootfs started failing in the default-bootstraps test. Here's some relevant log output:
+ rmdir /tmp/tmp.F339bZ5f02
++ chroot chroot lsb_release -c -s
+ suite=kinetic
++ chroot chroot lsb_release --release --short
+ version=22.10
++ tr '[:upper:]' '[:lower:]'
++ chroot chroot lsb_release --id --short
+ distro=ubuntu
+ prefix=
+ vmdk_f=
+ create_vmdk binary/
+ src=binary/
+ destination=
+ size=40960
+ streamconverter
++ mktemp -d
+ scratch_
+ cp binary/
+ truncate --size=40960M /tmp/tmp.
+ python3 -m VMDKstream /tmp/tmp.
Traceback (most recent call last):
File "/usr/lib/
outfile.
OSError: [Errno 28] No space left on device
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
return _run_code(code, main_globals, None,
File "/usr/lib/
exec(code, run_globals)
File "/usr/lib/
convert_
File "/usr/lib/
table_location = write_grain_
File "/usr/lib/
outfile.
OSError: [Errno 28] No space left on device
+ cleanup_vagrant
+ '[' -d /tmp/tmp.F339bZ5f02 ']'
+ rm -rf /tmp/tmp.DCEYPBmWm8 /tmp/tmp.KNQFZq36GP /tmp/tmp.F339bZ5f02 binary/
E: config/
P: Begin unmounting filesystems...
P: Saving caches...
P: Begin unmounting filesystems...
P: Saving caches...
autopkgtest [21:46:43]: test default-bootstraps: -------
autopkgtest [21:46:44]: test default-bootstraps: - -
Changed in livecd-rootfs (Ubuntu Kinetic): | |
status: | Triaged → Won't Fix |
It first started failing with version 2.775 and here's a log file:
https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- kinetic/ kinetic/ amd64/l/ livecd- rootfs/ 20220906_ 022021_ bba40@/ log.gz