Comment 21 for bug 1892358

Groovy
It seems this isn't over for groovy, it was mentioned that the issues in the subtest "tests-in-lxd" would be related to some fstab issues in those issues. But recently all architectures, but s390x recovered. I assume that the fstab issue is fixed but something else surfaces now.

groovy
  s390x
    tests-in-lxd (F 100% f 0% S 0% B 0% => P 0%/) FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    boot-and-services (F 3% f 0% S 0% B 0% => P 96%/) .....F........................
    systemd-fsckd (F 26% f 73% S 0% B 0% => P 0%/) ffffffffffffffffffffFFFFfFFfFF

We see when systemd-fsckd was marked flaky (F->f), but tests-in-lxd continues to perma-stop any migration depending on systemd.

Currently this holds back a lot of things in groovy, it seems to be:
qemu/1:5.0-5ubuntu7 chiark-tcl/1.3.4ubuntu3 cmake-extras/1.5-1ubuntu1 cstore-fdw/1.7.0-1 dateparser/0.7.4-1 dpdk/19.11.4-1 gem2deb/1.2.1 glibc/2.32-0ubuntu2 gnome-desktop3/3.37.90.1-1ubuntu1 grep/3.4-1 libnss-nis/3.1-0ubuntu3 libnss-nisplus/1.3-0ubuntu3 link-grammar/5.8.0-1 mksh/59b-1 natsort/7.0.1-1 openconnect/8.10-1 orafce/3.13.4-1 pandas/1.0.5+dfsg-3 pango1.0/1.46.1-1 php-nesbot-carbon/2.32.2-1 php-shellcommand/1.6.1-1 php-twig/2.13.0-1 postgresql-12/12.4-1 postgresql-common/216 postgresql-multicorn/1.4.0-2 reprotest/0.7.15 snapd/2.46.1+20.10 symfony/4.4.11+dfsg-1ubuntu1 systemd/246.4-1ubuntu1 tracker/2.3.4-1build1 vis/0.6-3

Therefore re-opening the groovy task, this isn't over yet :-/
@rbalint please let us know if you know more details about it already.