** Description changed:

  http://autopkgtest.ubuntu.com/packages/livecd-rootfs
  
  Log part from amd64:
  ...
  + udevadm settle
  + '[' -n /dev/mapper/loop0p1 -a -b /dev/mapper/loop0p1 ']'
  + '[' -e /etc/mtab ']'
  + apt-get -qqy install zerofree
  + e2fsck -y -E discard /dev/mapper/loop0p1
  e2fsck 1.43.4 (31-Jan-2017)
  cloudimg-rootfs: clean, 63584/274176 files, 284703/548091 blocks
  + zerofree /dev/mapper/loop0p1
  + rmdir mountpoint
  + clean_loops
  + '[' -n binary/boot/disk-uefi.ext4 ']'
  + kpartx -v -d binary/boot/disk-uefi.ext4
  device-mapper: remove ioctl on loop0p1 failed: Device or resource busy
  del devmap : loop0p15
  del devmap : loop0p14
  loop deleted : /dev/loop0
  + clean_loops
  + '[' -n binary/boot/disk-uefi.ext4 ']'
  + kpartx -v -d binary/boot/disk-uefi.ext4
  device-mapper: remove ioctl on loop0p1 failed: Device or resource busy
  loop deleted : /dev/loop0
  E: config/hooks/033-disk-image-uefi.binary failed (exit non-zero). You should 
check for errors.
  P: Begin unmounting filesystems...
  ...
+ 
+ [Impact]
+ 
+ * Having a working autopkgtest simplifies testing of future changes including
+   package SRUs thus backporting both the new autopkgtest test and the fix
+   making it succeed on every architecture seems to be beneficial.
+   (SRU-ing the test was suggested here: 
https://code.launchpad.net/~rbalint/livecd-rootfs/livecd-rootfs-autopkgtest/+merge/322322/comments/845316
 )
+ 
+ [Test Case]
+ 
+ * Run the autopkgtest test itself. It also covers the parts needed to be
+   changed for making the test pass, including the part changed in this bug.
+ 
+ [Regression potential]
+ 
+ * Livecd-rootfs scripts had to be changed to make the autopkgtest test pass.
+   The changes could make livecd-rootfs generate broken/invalid images, but
+   this is highly unlikely because changes with regressions would also break
+   the test.

** Description changed:

  http://autopkgtest.ubuntu.com/packages/livecd-rootfs
  
  Log part from amd64:
  ...
  + udevadm settle
  + '[' -n /dev/mapper/loop0p1 -a -b /dev/mapper/loop0p1 ']'
  + '[' -e /etc/mtab ']'
  + apt-get -qqy install zerofree
  + e2fsck -y -E discard /dev/mapper/loop0p1
  e2fsck 1.43.4 (31-Jan-2017)
  cloudimg-rootfs: clean, 63584/274176 files, 284703/548091 blocks
  + zerofree /dev/mapper/loop0p1
  + rmdir mountpoint
  + clean_loops
  + '[' -n binary/boot/disk-uefi.ext4 ']'
  + kpartx -v -d binary/boot/disk-uefi.ext4
  device-mapper: remove ioctl on loop0p1 failed: Device or resource busy
  del devmap : loop0p15
  del devmap : loop0p14
  loop deleted : /dev/loop0
  + clean_loops
  + '[' -n binary/boot/disk-uefi.ext4 ']'
  + kpartx -v -d binary/boot/disk-uefi.ext4
  device-mapper: remove ioctl on loop0p1 failed: Device or resource busy
  loop deleted : /dev/loop0
  E: config/hooks/033-disk-image-uefi.binary failed (exit non-zero). You should 
check for errors.
  P: Begin unmounting filesystems...
  ...
  
  [Impact]
  
  * Having a working autopkgtest simplifies testing of future changes including
-   package SRUs thus backporting both the new autopkgtest test and the fix
-   making it succeed on every architecture seems to be beneficial.
-   (SRU-ing the test was suggested here: 
https://code.launchpad.net/~rbalint/livecd-rootfs/livecd-rootfs-autopkgtest/+merge/322322/comments/845316
 )
+   package SRUs thus backporting both the new autopkgtest test and the fix
+   making it succeed on every architecture seems to be beneficial.
+   (SRU-ing the test was suggested here: 
https://code.launchpad.net/~rbalint/livecd-rootfs/livecd-rootfs-autopkgtest/+merge/322322/comments/845316
 )
  
  [Test Case]
  
  * Run the autopkgtest test itself. It also covers the parts needed to be
-   changed for making the test pass, including the part changed in this bug.
+   changed for making the test pass, including the part changed in this bug.
  
- [Regression potential]
+ [Regression Potential]
  
  * Livecd-rootfs scripts had to be changed to make the autopkgtest test pass.
-   The changes could make livecd-rootfs generate broken/invalid images, but
-   this is highly unlikely because changes with regressions would also break
-   the test.
+   The changes could make livecd-rootfs generate broken/invalid images, but
+   this is highly unlikely because changes with regressions would also break
+   the test.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684090

Title:
  Autopkgtest is failing on most architectures, ppc64el passes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1684090/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to