[Bug 1881947] Autopkgtest regression report (systemd/237-3ubuntu10.44)

Ubuntu SRU Bot 1881947 at bugs.launchpad.net
Tue Jan 12 12:49:03 UTC 2021


All autopkgtests for the newly accepted systemd (237-3ubuntu10.44) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-4.15/4.15.0-1104.116 (amd64)
munin/2.0.37-1ubuntu0.1 (arm64)
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
libvirt/4.0.0-1ubuntu8.17 (i386)
apt/1.6.12ubuntu0.2 (armhf)
netplan.io/0.99-0ubuntu3~18.04.3 (amd64)
linux-hwe-5.0/5.0.0-63.69 (armhf)
openssh/1:7.6p1-4ubuntu0.3 (armhf, s390x, ppc64el, arm64, i386, amd64)
corosync/2.4.3-0ubuntu1.1 (armhf)
nut/2.7.4-5.1ubuntu2 (i386)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Autopkgtest fails due to corrupted journal file

  [Test Case]

   * Observe autopkgtest root-unittests not failing with:

  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

  [Where problems could occur]

   * The change has no impact on the systemd binary packages. The
  relaxed test could hide a journal corruption problem, but it seems the
  corrupted journal files occur only on arm64 probably due to arm64
  reboots being resets: LP: #1748280.

  [Original Bug Text]

  Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1:
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz

  [...]
  PASS: test-journal-enum
  ====== test-journal-flush =======
  Root directory /var/log/journal removed.
  Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed.
  mmap cache statistics: 739 hit, 5 miss
  journal_file_copy_entry failed: Bad message
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.
  FAIL: test-journal-flush (code: 134)
  Aborted (core dumped)
  ====== test-journal-importer =======
  [...]
  autopkgtest [07:17:29]: @@@@@@@@@@@@@@@@@@@@ summary
  timedated            PASS
  hostnamed            PASS
  localed-locale       PASS
  localed-x11-keymap   PASS
  logind               PASS
  unit-config          PASS
  storage              PASS
  networkd-test.py     PASS
  build-login          PASS
  boot-and-services    PASS
  udev                 PASS
  root-unittests       FAIL non-zero exit status 134
  upstream             PASS
  boot-smoke           PASS
  systemd-fsckd        PASS
  Exit request sent.
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1881947/+subscriptions



More information about the foundations-bugs mailing list