That's not what I meant. The test is valid, and on s390x, one consistently fails to run fsckd right.
I have already included a few overrides in bionic, where it is valid for fsckd to enter error state, as long as it does not block boot. what release are you seeing this? what you are saying here, is that fsck support on boot is broken on s390x, and that we do not care about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754472 Title: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there Status in systemd package in Ubuntu: New Bug description: The test really seems to be triggered all of the time to resolve a flaky test. That is just not worth the test. But it provides goo coverage, so an override in britney would loose all that. Lets skip the offending test on the arch it is known to be flaky (s390x). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
