So the only new autopkgtest failures are:
> 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" == "")
this is the first test failure on trusty/armhf:
http://autopkgtest.ubuntu.com/packages/umockdev/trusty/armhf
however, it's failed for xenial, yakkety, and zesty on armhf for a long time,
with the same failure:
http://autopkgtest.ubuntu.com/packages/umockdev/xenial/armhf
http://autopkgtest.ubuntu.com/packages/umockdev/yakkety/armhf
http://autopkgtest.ubuntu.com/packages/umockdev/zesty/armhf
so it seems like whatever was causing the failures for X/Y/Z on armhf is
now also causing the failure for trusty on armhf; I think it's unlikely
a systemd change caused the failure.
> 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.
Closer looks shows it's complaining about the JSON data, the test was
expecting a comment:
(null): Detected invalid serialisation data: expected comment
test_state: tests/test_state.c:4048: test_upstart_with_apparmor_upgrade:
Assertion `(state_from_string (json_string)) == 0' failed.
I can't tell why it's failing now but not before, but it's also hard to
see any relation between a systemd/udev update and upstart JSON
serialization failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647485
Title:
NVMe symlinks broken by devices with spaces in model or serial strings
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1647485/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
