[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#958733: genext2fs: autopkgtest failure on arm64: libguestfs: error: appliance closed the connection unexpectedly.



Source: genext2fs
Version: 1.4.2-2
X-Debbugs-CC: debian-ci@lists.debian.org
Severity: serious
User: debian-ci@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

With a recent upload of genext2fs you added an autopkgtest, great.
However, it fails on arm64.

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=genext2fs

https://ci.debian.net/data/autopkgtest/testing/arm64/g/genext2fs/5128192/log.gz

I: Unpacking the base system...
I: Base system installed successfully.
+ tar --numeric-owner --sort=name -C rootfs.in -cf rootfs.in.tar .
+ du --apparent-size --block-size 1024 --summarize rootfs.in
+ cut -f 1
+ numblocks=184608
+ numblocks=203068
+ genext2fs -B 1024 -b 203068 -d rootfs.in rootfs.dir.img
+ rm -rf rootfs.in
+ genext2fs -B 1024 -b 203068 -N 0 rootfs.tar.img
+ genext2fs -B 1024 -b 203068 -N 0 rootfs2.tar.img
+ cmp rootfs.tar.img rootfs2.tar.img
+ rm rootfs2.tar.img
+ guestfish add-ro rootfs.dir.img : run : mount /dev/sda / : tar-out /
rootfs.tar
*stdin*:0: libguestfs: error: appliance closed the connection unexpectedly.
This usually means the libguestfs appliance crashed.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
*stdin*:0: libguestfs: error: /usr/bin/qemu-system-aarch64 exited with
error status 1.
To see full error messages you may need to enable debugging.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
*stdin*:0: libguestfs: error: guestfs_launch failed.
This usually means the libguestfs appliance failed to start or crashed.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
autopkgtest [16:59:46]: test general: -----------------------]

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: