> 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" == "")
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
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.
So the only new autopkgtest failures are:
> Regression in autopkgtest for umockdev (armhf): test log
this fails with: test-umockdev- record. c:706:t_ system_ single: assertion failed (_tmp10_ == ""): ("Cannot access device /dev/loop0: No such file or directory\n" == "")
ERROR:tests/
this is the first test failure on trusty/armhf: autopkgtest. ubuntu. com/packages/ umockdev/ trusty/ armhf
http://
however, it's failed for xenial, yakkety, and zesty on armhf for a long time, with the same failure: autopkgtest. ubuntu. com/packages/ umockdev/ xenial/ armhf autopkgtest. ubuntu. com/packages/ umockdev/ yakkety/ armhf autopkgtest. ubuntu. com/packages/ umockdev/ zesty/armhf
http://
http://
http://
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: state.c: 4048: test_upstart_ with_apparmor_ upgrade: Assertion `(state_from_string (json_string)) == 0' failed.
test_state: tests/test_
Closer looks shows it's complaining about the JSON data, the test was expecting a comment:
(null): Detected invalid serialisation data: expected comment state.c: 4048: test_upstart_ with_apparmor_ upgrade: Assertion `(state_from_string (json_string)) == 0' failed.
test_state: tests/test_
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.