Comment 13 for bug 1732032

I had a super nice and detailed reply written here, but of course I lost it. Browsers are stupid things sometimes. So here are the comments that survived.

TL;DR:
firejail is known to fail on s390 because there is no thunderbird package for a mainframe. I emailed ubuntu-devel@ and also pinged #ubuntu-devel on irc. Switching the test bed from a container to a VM for s390 a while back allowed this new test to run.

Others are green, with the exception of trusty:
a) armhf: fails copying the device /dev/null elsewhere with -a, which equates to creating a device outside of tmp, which is forbidden. Last time this worked was when the test bed was on lxc in 2016. On lxd it doesn't work. The other architectures are not using lxd. We should probably add a constraint so that the test only runs in vms. Should it be added to the current SRU package for trusty?

b) ppc: a grub error:
Generating grub configuration file ...
grub-probe: error: not a directory.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1

I pinged #ubuntu-devel about it, since I have no idea how to setup and run a ppc vm, but got no response:

https://irclogs.ubuntu.com/2017/12/07/%23ubuntu-devel.html#t19:33

ahasenack is there something going on with setting up ppc64el autopkg tests in excuses? I have 3 different packages failing there with the same error 19:33
ahasenack grub-probe: error: not a directory. 19:33
ahasenack run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 19:33
ahasenack in trusty 19:33
ahasenack https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/a/autopkgtest/20171207_002904_c5112@/log.gz is one of them

Got no response. I don't even know if grub is used in ppc.

Regarding amd64 smoke test, I've been using the updated package on my machine (artful/amd64).