Comment 37 for bug 1647485

> Could someone please look at the autopkgtest regressions in http://people.canonical.com/~ubuntu-
> archive/pending-sru.html against systemd please?

I'll ignore the no-longer-supported LTS kernel tests, so that leaves:

> Regression in autopkgtest for network-manager (ppc64el): test log

This has been failing since late 2015, with the same failure each time.
http://autopkgtest.ubuntu.com/packages/n/network-manager/trusty/ppc64el

> Regression in autopkgtest for linux-lts-xenial (ppc64el): test log
> Regression in autopkgtest for linux-lts-xenial (i386): test log
> Regression in autopkgtest for linux-lts-xenial (armhf): test log

These are failing either because the running and test kernel versions don't match, or because the test timed out. Again, they appear to have been failing for a long time; no new failures for the latest systemd.

> Regression in autopkgtest for ubuntu-drivers-common (i386): test log

another test that's failed for a long time in the same way each time. nothing new.

> Regression in autopkgtest for umockdev (armhf): test log

this fails with:
ERROR:tests/test-umockdev-record.c:706:t_system_single: assertion failed (_tmp10_ == ""): ("Cannot access device /dev/loop0: No such file or directory\n" == "")

it's not clear why there's no /dev/loop0, and previous test runs didn't fail.

> Regression in autopkgtest for open-iscsi (armhf): test log

this has failed the same way for the last 6 tests, because open-iscsi isn't running. Not sure what introduced that, but it happened before the last systemd update.

> Regression in autopkgtest for upstart (amd64): test log

this fails with:
test_state: tests/test_state.c:4048: test_upstart_with_apparmor_upgrade: Assertion `(state_from_string (json_string)) == 0' failed.

obviously not a helpful test failure message.