"and so causes autopkgtest failures." is not true. >From http://autopkgtest.ubuntu.com/packages/systemd/bionic/amd64 E.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20190529_090547_1f40a@/log.gz
Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... unexpected success FAILED (unexpected successes=1) autopkgtest [09:05:38]: test systemd-fsckd: -----------------------] systemd-fsckd PASS Note systemd-fsckd only fails on failures & errors, and passed with unexpected successes: if len(result.failures) != 0 or len(result.errors) != 0: return_code = 1 I also wonder what has changed to make this test case reliable, in the past it used to be flakey, that's why i switched it to expectedfailure. I guess it's ok to reenable this in devel. I see no need to reenable it in stable series. It has a regression potential, since it used to be flakey, it may start to be flakey again blocking SRU migrations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829450 Title: test_systemd_fsck_with_plymouth_failure passes but marked expected failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs