systemd: adt test failures againt Ubuntu-4.4.0-4.19 -- systemd-fsckd failing

Bug #1543144 reported by Andy Whitcroft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Released
Undecided
Martin Pitt

Bug Description

Ran 1 test in 25.833s

OK
test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest)
Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... bash: line 1: 803 Killed /tmp/adt-run.hMnUaN/build.VCo/systemd-228/debian/tests/systemd-fsckd 2> >(tee -a /tmp/adt-run.hMnUaN/systemd-fsckd-stderr >&2) > >(tee -a /tmp/adt-run.hMnUaN/systemd-fsckd-stdout)
adt-run [20:40:20]: test process requested reboot with marker test_systemd_fsck_with_plymouth_failure:0
Connection to 10.220.43.4 closed by remote host.
adt-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...
adt-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...
adt-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...
test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest)
Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... FAIL

Revision history for this message
Martin Pitt (pitti) wrote :
Changed in systemd (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.3 KiB)

This bug was fixed in the package systemd - 228-6ubuntu1

---------------
systemd (228-6ubuntu1) xenial; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
    - Hack to support system-image read-only /etc, and modify files in
      /etc/writable/ instead.
    - Build using libseccomp on powerpc and ppc64el (See Debian #800818).

    Upgrade fixes, keep until 16.04 LTS release:
    - systemd Conflicts/Replaces/Provides systemd-services.
    - Remove obsolete systemd-logind upstart job.
    - Clean up obsolete /etc/udev/rules.d/README.
    - systemd.postinst: Migrate mountall specific fstab options to standard
      util-linux "nofail" option.
    - systemctl: Don't forward telinit u to upstart. This works around
      upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
      that changes to point to systemd during the upgrade. This avoids running
      systemd during a dist-upgrade. (LP: #1430479)
    - Provide shutdown fallback for upstart. (LP: #1370329)
    - Break lvm (<< 2.02.133-1ubuntu1) and remove our dummy /etc/init.d/lvm2
      on upgrades, as it's shipped by lvm2 now.
    - Make udev break on mdadm << 3.3-2ubuntu3, as udev's init script dropped
      the "Provides: raid-mdadm".
    - Clean up /var/log/udev on upgrade (which is written under upstart, but
      not under systemd). (LP: #1537211)
    - Migrate existing s390x network configuration to new names. (LP: #1526808)
    - systemd.postinst: Bump Version comparison for migrating the UTC setting
      from /etc/default/rcS to /etc/adjtime, to run it for upgrades to 16.04.

systemd (228-7) UNRELEASED; urgency=medium

  * debian/tests/systemd-fsckd: Tame overly strict test for failed plymouth
    unit, which is a race condition with plymouthd auto-stopping.
    (LP: #1543144)
  * Do not warn about Wants depencencies on masked units. (LP: #1543282)
  * Drop timedated-don-t-rely-on-usr-being-mounted-in-the-ini.patch.
    initramfs-tools has mounted /usr since Jessie, and tzdata now creates
    /etc/localtime as a symlink too (see #803144).
  * Use-different-default-paths-for-various-binaries.patch: Drop path changes
    for setcap (which is already a build dep and not used at all) and sulogin
    (which is now in util-linux).
  * Remove obsolete udev maintainer script checks:
    - Drop check for kernel >= 2.6.32, which released in 2009.
    - Drop restarting of some daemons due to the devtmpfs migration, which
      happened before the above kernel even.
    - Drop support for forcing upgrades on kernels known not to work via
      /etc/udev/kernel-upgrade. Don't pretend that this would help, as users
      could end up with a non-bootable system. Always fail early in preinst
      when it's still possible to install a working kernel.
    - Drop postinst test for "running in containers" -- it's actually possible
      to run udev in containers if you mount /sys r/w and you know what you
      are doing. Also, the init.d script and systemd service do that check
      again.
    - Keep the kernel feature and chroot checks, as these are still useful.
      Simplify check_kernel_features() by eliminating some variables.
    - Drop debconf templ...

Read more...

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.