Comment 0 for bug 1736955

The systemd-fsckd test has a constraint of isolation-machine, among others. Until recently, that actually prevented it from running on s390 because we were using containers for it.

About 3 weeks ago, apparently we started using VMs for s390 dep8 tests, so that constraint was finally satisfied and systemd-fsckd started to run. And to fail consistently, as can be see in http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x:

Traceback (most recent call last):
  File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", line 267, in <module>
    boot_with_systemd_distro()
  File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", line 243, in boot_with_systemd_distro
    enable_plymouth()
  File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", line 224, in enable_plymouth
    plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'

There is no grub for s390, so this test must be skipped in that architecture.