-
Committer:
christian.ehrhardt at canonical
-
Date:
2020-09-16 06:11:50 UTC
-
Revision ID:
christian.ehrhardt@canonical.com-20200916061150-flexfry9h8xwsg34
force-badtest systemd (LP: #1892358)
Regression due to test env change made the systemd-fsckd way too flaky.
As discussed in (LP: #1892358) it has to be marked flaky. Mark it as badtest
until an SRU does so.
Non x86 arches seem not to hit this in Bionic, so they are not marked.
Last 20 test results on Bionic:
bionic
amd64
boot-and-services (F 5% f 0% S 0% B 5% => P 90%/) ..............B..F..
boot-smoke (F 10% f 0% S 0% B 5% => P 85%/) .........F..F.B.....
upstream (F 5% f 0% S 0% B 5% => P 90%/) ..............B..F..
systemd-fsckd (F 70% f 0% S 0% B 5% => P 25%/) FFF..F.F.FFFFFBF.FFF
root-unittests (F 5% f 0% S 0% B 5% => P 90%/) ..............B..F..
armhf
no failures
ppc64el
upstream (F 5% f 0% S 0% B 0% => P 95%/) ...........F........
systemd-fsckd (F 10% f 0% S 0% B 0% => P 90%/) ..............F...F.
s390x
boot-and-services (F 5% f 0% S 0% B 0% => P 95%/) .F..................
i386
boot-smoke (F 5% f 0% S 0% B 5% => P 90%/) ...F..B.............
upstream (F 15% f 0% S 0% B 5% => P 80%/) ..F...B.....F.....F.
systemd-fsckd (F 60% f 0% S 0% B 5% => P 35%/) .F.FFFBFFFFFF.F..F..