Merge lp:~ahasenack/britney/ocfs2-tools-hints-1.8.5-5ubuntu1 into lp:britney

[Andreas Hasenack]

Update the ocfs2-tools badtest hint to 1.8.5-5ubuntu1, as it still doesn't work in s390x.

Update the ocfs2-tools badtest hint to 1.8.5-5ubuntu1, as it still doesn't work in s390x. See upstream bug at https://github.com/markfasheh/ocfs2-tools/issues/22.

Unmerged revisions

3155. By Andreas Hasenack on 2018-07-31

Update the ocfs2-tools badtest hint to 1.8.5-5ubuntu1, as it still doesn't
work in s390x.

3154. By Łukasz Zemczak on 2018-07-30

badtest systemd/arm64

3153. By Stefano Rivera on 2018-07-28

Unknown regression

3152. By Stefano Rivera on 2018-07-28

Bump python-xarray (arm64 only)

3151. By Andy Whitcroft on 2018-07-27

linux: s390x issues kicking that can

Signed-off-by: Andy Whitcroft <email address hidden>

3150. By Andy Whitcroft on 2018-07-25

linux: primary kernel is now a direct upload -- drop unblock too

Signed-off-by: Andy Whitcroft <email address hidden>

3149. By Andy Whitcroft on 2018-07-25

linux: primary kernel is now a direct upload.

Signed-off-by: Andy Whitcroft <email address hidden>

3148. By Andy Whitcroft on 2018-07-25

kernels: unblock now released copies

Signed-off-by: Andy Whitcroft <email address hidden>

3147. By Steve Langasek on 2018-07-24

pinentry fluke pass on amd64 also

3146. By Iain Lane on 2018-07-24

bump udisks2

=== added file 'adconrad'
--- adconrad	1970-01-01 00:00:00 +0000
+++ adconrad	2018-07-31 19:04:17 +0000
@@ -0,0 +1,54 @@
+# Racy tests are not worth blocking every SRU ever on:
+force-badtest open-iscsi/2.0.874-5ubuntu2/amd64
+# This has been flapping forever and is brute-forced with retries:
+force-badtest haskell-hoogle/all/arm64
+# Regressed in release pocket:
+force-badtest mash/2.0-2/armhf
+force-badtest node-chokidar/1.7.0-1/s390x node-chokidar/1.7.0-2/s390x
+force-badtest node-platform/1.3.4-3/s390x node-platform/1.3.5-1/s390x
+force-badtest node-yargs/10.0.3-2
+# These tests fail now that s390x provides isolation-machine:
+force-badtest dahdi-linux/all/s390x
+force-badtest gsequencer/1.4.24-1/s390x
+force-badtest libdata-uuid-libuuid-perl/0.05-3build1/s390x
+# Test is flaky on all arches, it's a miracle it passed once:
+force-badtest pglogical/2.2.0-1
+# New 2.x tests fail on armhf due to slow I/O
+force-badtest pgbackrest/2.02-1/armhf
+# Depends on x86-only libngs-java
+force-badtest beagle/all/armhf beagle/all/ppc64el beagle/all/s390x
+force-badtest fastqc/all/armhf fastqc/all/ppc64el fastqc/all/s390x
+# Depends on stuff no longer built:
+force-badtest libcatmandu-store-mongodb-perl/all/i386
+force-badtest roary/all/armhf roary/all/s390x
+force-badtest pbgenomicconsensus/all/i386
+# Not built on i386, the test might not work:
+force-badtest pbh5tools/all/i386
+# Mysteriously passed once, and never again:
+force-badtest vagrant-libvirt/0.0.40-1/amd64 vagrant-libvirt/0.0.40-1/s390x vagrant-libvirt/0.0.43-2/amd64 vagrant-libvirt/0.0.43-2/s390x
+# Regression exists in release and proposed:
+force-badtest r-bioc-annotationhub/2.10.1-1 r-bioc-annotationhub/2.12.0-2 r-bioc-annotationhub/2.12.0+dfsg-1
+force-badtest r-bioc-biocparallel/1.12.0-2/s390x r-bioc-biocparallel/1.12.0-2/armhf
+force-badtest r-bioc-biocparallel/1.14.0-2/s390x r-bioc-biocparallel/1.14.0-2/armhf
+force-badtest r-bioc-biocparallel/1.14.1-1build1/s390x r-bioc-biocparallel/1.14.1-1build1/armhf
+force-badtest r-bioc-biocparallel/1.14.2-1/s390x r-bioc-biocparallel/1.14.2-1/armhf
+# debootstrap's tests are a flaming heap in containers:
+force-badtest debootstrap/all/s390x
+# fails only on lxc hosts
+force-badtest sbuild/all/armhf
+# profnet-snapfun test is regressed in both release and proposed:
+force-badtest profnet/1.0.22-5
+# opening unblocks:
+unblock distro-info-data/0.37ubuntu1
+unblock base-files/10.1ubuntu3
+unblock vim/2:8.0.1453-1ubuntu2
+# docker tests can't pass untl lxd cosmic images exist
+force-skiptest vim/2:8.0.1453-1ubuntu2
+unblock debootstrap/1.0.95ubuntu1
+# lxc tests can't pass until lxc images exist
+force-skiptest debootstrap/1.0.95ubuntu1
+unblock iso-scan/1.55ubuntu6
+unblock choose-mirror/2.78ubuntu4
+unblock preseed/1.71ubuntu8
+unblock cdrom-detect/1.57ubuntu6
+unblock debian-installer/20101020ubuntu544
 
=== added file 'apw'
--- apw	1970-01-01 00:00:00 +0000
+++ apw	2018-07-31 19:04:17 +0000
@@ -0,0 +1,45 @@
+# While copying kernels forward from xenial it rather too easy for linux
+# to slip out without the testing being fully reviewed.  As britney is not
+# able to track previous failures correctly for kernels.
+#block linux
+block linux-raspi2
+block linux-oem
+block linux-aws
+block linux-azure
+block linux-gcp
+block linux-kvm
+
+# Development kernel unblocks:
+#unblock linux/4.15.0-23.25
+unblock linux-raspi2/4.15.0-1017.18
+unblock linux-oem/4.15.0-1012.15
+unblock linux-aws/4.15.0-1016.16
+unblock linux-azure/4.15.0-1018.18
+unblock linux-gcp/4.15.0-1014.14
+unblock linux-kvm/4.15.0-1016.16
+
+#
+# arm* removed in zesty-proposed hint in-progress tests against them.
+force-badtest sunpy/all/armhf
+
+# dkms failures here are actually kernel 4.9 related
+force-badtest kpatch/0.3.2-3ubuntu1
+
+# python-pysam does not (and never has) built on armhf and i386
+force-badtest python-pysam/all/armhf python-pysam/all/i386
+
+# ginggs -- monkeysign ... unexpected pass
+force-badtest monkeysign/2.2.3/i386 monkeysign/2.2.3/armhf monkeysign/2.2.3/ppc64el
+
+# kde is splittins apps out of this package, it is not relevant to those split apps.
+force-badtest kde-baseapps/4:16.04.3-0ubuntu1
+
+# 14-feb-2017: armhf test non-installable
+force-badtest python-cobra/all/armhf
+
+# python-scipy/i386 is failing due a bug in the tests, do not want to trigger
+# a whole new set of tests to fix it.
+force-badtest python-scipy/0.19.1-2ubuntu1/i386
+
+# linux-gcp/armhf -- does not even build here, so tests here cannot be relevant
+force-badtest linux-gcp/all/armhf
 
=== added file 'arges'
=== added file 'brian-murray'
=== added file 'cjwatson'
=== added file 'freeze'
=== added file 'jriddell'
=== added file 'kitterman'
=== added file 'laney'
--- laney	1970-01-01 00:00:00 +0000
+++ laney	2018-07-31 19:04:17 +0000
@@ -0,0 +1,34 @@
+# regressed in release; some valgrind leaks: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1763628
+force-badtest colord/1.3.3-2build1
+
+# doko removed pdftk which this depends on...
+force-badtest dmalloc/5.5.2-10
+
+# isolation-machine, needs thunderbird which isn't available
+force-badtest firejail/all/s390x
+
+# passed once by fluke on armhf it seems
+
+force-badtest ostree/all/armhf
+
+# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772
+force-badtest libreoffice/1:6.0.6~rc1-0ubuntu1/i386
+
+# mongo isn't built for armhf/i386 any more
+force-badtest flask-mongoengine/all/i386
+force-badtest mongodb/all/i386
+force-badtest flask-mongoengine/all/armhf
+force-badtest mongodb/all/armhf
+
+# FTBFS, no package on this arch, unclear how it passed(!)
+force-badtest python-fitsio/all/armhf
+
+# Field3D only supports Ogawa-backed files on little-endian systems.
+force-badtest field3d/all/s390x
+
+# @INC problem; not perl 5.24
+force-badtest eekboek/2.02.05+dfsg-2
+
+# bad test which fails if the test runner can't reach the public Internet.
+# LP: #1427982
+force-badtest libtest-requiresinternet-perl/0.05-2
 
=== added file 'pitti'
--- pitti	1970-01-01 00:00:00 +0000
+++ pitti	2018-07-31 19:04:17 +0000
@@ -0,0 +1,55 @@
+# new PEP-8 errors with zesty's newer pep8 tool; don't bump!
+force-badtest rpmlint/1.9-6
+
+# segfaults on 32 bit
+force-badtest baloo-kf5/all/i386 baloo-kf5/all/armhf
+
+# started failing with move to lxd on armhf
+force-badtest pbuilder/all/armhf
+
+#
+# blacklisted for test runs as they kill testbeds
+#
+#
+force-badtest stress-ng/blacklisted/ppc64el
+
+#
+# flaky, universe, nobody cares in Ubuntu
+#
+#
+force-badtest beets/all/s390x
+# times out
+force-badtest c2esp/all/armhf
+force-badtest debci/1.7.1
+force-badtest elasticsearch-curator/5.2.0-1
+# takes painfully long, times out on armhf, testing on x86 is enough
+force-badtest epson-inkjet-printer-escpr/all/armhf
+force-badtest gjs/all/s390x
+force-badtest jsurf-alggeo/0.3.0+ds-1
+force-badtest libcgi-application-plugin-captcha-perl/0.04-2
+# broken test if git is installed
+force-badtest libdist-zilla-plugin-githubmeta-perl/0.52-1
+force-badtest mercurial/all/armhf
+# flaky on s390x, alwaysfail on others
+force-badtest palabos/s390x/all
+force-badtest pdns/all
+force-badtest pbsuite/all/i386
+force-badtest php-horde-http/2.1.7-1 php-horde-http/2.1.7-3
+force-badtest php-horde-icalendar/all/armhf php-horde-icalendar/all/i386
+force-badtest python-publicsuffix/1.1.0-2
+force-badtest pyzmq/all/s390x pyzmq/all/armhf
+force-badtest rexical/1.0.5-2build1
+force-badtest ruby-amq-protocol/all/s390x
+force-badtest ruby-augeas/1:0.5.0-3build6
+# Debian #816161
+force-badtest ruby-awesome-print/1.6.1-2
+force-badtest ruby-kaminari/0.17.0-3
+force-badtest ruby-minitest-excludes/2.0.0-1
+force-badtest ruby-mixlib-shellout/2.2.6-1
+force-badtest ruby-rack/1.6.4-4
+force-badtest ruby-roadie-rails/1.1.0-1
+force-badtest ruby-sshkit/all/s390x
+force-badtest ruby-test-unit/3.2.5-1/amd64
+force-badtest ruby-webmock/3.0.1-1
+force-badtest s3ql/2.26+dfsg-1ubuntu1
+force-badtest zodb/1:3.10.7-1build1/ppc64el zodb/1:3.10.7-1build1/s390x
 
=== added file 'racb'
=== added file 'raof'
=== added file 'sil2100'
--- sil2100	1970-01-01 00:00:00 +0000
+++ sil2100	2018-07-31 19:04:17 +0000
@@ -0,0 +1,25 @@
+# Something broke ubuntu-image tests completely (LP: #1775084, LP: #1775085)
+force-badtest ubuntu-image/1.3+18.04ubuntu2
+
+# Release broke the liggghts armhf tests which are now failing, plans of removing the armhf binary
+force-badtest liggghts/3.7.0+repack1-1build1/armhf
+
+# These tests should never pass - was Always Failed until unexpectedly passing once. The suite is not ready yet. Actually, when it passed it actually failed, just status is wrongly reported.
+force-badtest pyfai/0.15.0+dfsg1-1/amd64 pyfai/0.15.0+dfsg1-1/arm64
+
+# Some more R badtests that are failing, some of which basically from the start
+force-badtest r-cran-rmarkdown/1.10+dfsg-1/armhf r-cran-rmarkdown/1.10+dfsg-1/s390x
+force-badtest r-cran-yaml/2.1.19-1ubuntu1/i386
+force-badtest r-cran-memoise/1.1.0-2/armhf
+
+# These tests are broken and worked on, but until then we would need to unblock some migrations (see #896635 in Debian)
+force-badtest python-scipy/0.19.1-2ubuntu1/amd64
+
+# Flaky tests, timing-out constantly, never passed for the new version (LP: #1780767)
+force-badtest apport/2.20.10-0ubuntu6/amd64
+
+# Known issues in s390x testing.
+force-badtest linux/4.17.0-6.7/s390x
+
+# Test passed only once but apparently it's still broken with the new version, so not really a regression
+force-badtest systemd/239-7ubuntu1/arm64
 
=== added file 'stefanor'
--- stefanor	1970-01-01 00:00:00 +0000
+++ stefanor	2018-07-31 19:04:17 +0000
@@ -0,0 +1,12 @@
+# autodep8 bug #832567
+force-badtest ruby-cucumber-wire/0.0.1-2
+
+# -2 was flakey too
+force-badtest octave-symbolic/2.6.0-3build1/s390x
+
+# from ginggs: new tests regress
+# https://github.com/numpy/numpy/issues/8325
+force-badtest python-xarray/0.10.7-1/arm64 python-xarray/0.10.8-1/arm64
+
+# Unknown regression, raised by ginngs
+force-badtest cmake-extras/1.3+17.04.20170310-1ubuntu4/ppc64el
 
=== added file 'stgraber'
--- stgraber	1970-01-01 00:00:00 +0000
+++ stgraber	2018-07-31 19:04:17 +0000
@@ -0,0 +1,2 @@
+# snapcraft adt broken on maven test
+force-badtest snapcraft/2.40+18.04.3
 
=== added file 'tjaalton'
--- tjaalton	1970-01-01 00:00:00 +0000
+++ tjaalton	2018-07-31 19:04:17 +0000
@@ -0,0 +1,3 @@
+# hardly ever passes, blocks pyasn1 from migrating
+force-badtest bdfproxy/0.3.9-1/amd64
+
 
=== added file 'ubuntu-release'
--- ubuntu-release	1970-01-01 00:00:00 +0000
+++ ubuntu-release	2018-07-31 19:04:17 +0000
@@ -0,0 +1,126 @@
+# passed previously in containers, now fails everywhere
+force-badtest ruby-fakeweb/1.3.0+git20131202.48208f9+dfsg-3 ruby-fakeweb/1.3.0+git20170806+dfsg1-1
+
+# regressed in release
+force-badtest adequate/0.15.1ubuntu5
+force-badtest afl/2.52b-2
+force-badtest apt-clone/0.4.1ubuntu2
+force-badtest celery/4.1.0-2ubuntu1
+force-badtest conntrack-tools/1:1.4.4+snapshot20161117-6ubuntu2/armhf
+force-badtest dh-ada-library/6.12
+force-badtest ganeti/2.16.0~rc2-1build1/i386 ganeti/2.16.0~rc2-1build1/armhf
+force-badtest libfile-userconfig-perl/0.06-4/i386
+force-badtest libgeo-coder-googlev3-perl/0.16-1/i386
+force-badtest libterm-filter-perl/0.03-2/arm64
+force-badtest lintian/2.5.81ubuntu1
+force-badtest log4cxx/0.10.0-13ubuntu1
+force-badtest node-cache-base/0.8.4-1
+force-badtest node-external-editor/2.0.4+dfsg-1
+force-badtest octave-tisean/0.2.3-3
+force-badtest python-ruffus/2.6.3+dfsg-4/amd64 python-ruffus/2.6.3+dfsg-5/amd64 python-ruffus/2.7-1/amd64
+force-badtest ruby-pkg-config/1.2.9-1
+force-badtest ruby-rspec-puppet/2.6.1-1
+force-badtest sextractor/2.19.5+dfsg-5/amd64 sextractor/2.19.5+dfsg-6/amd64
+force-badtest stunnel4/3:5.44-1ubuntu2
+force-badtest twisted/17.9.0-1 twisted/17.9.0-2
+force-badtest vagrant-lxc/1.2.1-3ubuntu1/amd64 vagrant-lxc/1.4.0-1/amd64
+force-badtest xen-tools/4.7-1/arm64
+force-badtest yorick/2.2.04+dfsg1-7 yorick/2.2.04+dfsg1-9
+force-badtest systemd/237-3ubuntu10/ppc64el systemd/237-3ubuntu10/amd64 systemd/237-3ubuntu10/i386
+
+# skip tests that fail now that s390x has full VMs
+force-badtest vagrant-lxc/1.2.1-3ubuntu1/s390x vagrant-lxc/1.4.0-1/s390x
+# Was skipped in lxc, never passed in a vm, questionable usefulness on s390x/ppc64el given it tests usb camera...
+force-badtest gvfs/1.36.1-0ubuntu1/ppc64el gvfs/1.36.1-0ubuntu1/s390x gvfs/1.36.1-0ubuntu3/ppc64el gvfs/1.36.1-0ubuntu3/s390x
+
+# tests broken with proxy
+force-badtest golang-github-hashicorp-atlas-go/0.0~git20170808.8261ea0-1 golang-github-hashicorp-atlas-go/0.0~git20170808.8261ea0-3
+
+# primer3 builds binary-all package but binary-arch package removed on architecture
+force-badtest primer3/2.4.0-1ubuntu1/s390x primer3/2.4.0-1ubuntu2/s390x
+force-badtest libbio-primerdesigner-perl/0.07-5/s390x
+
+# flaky
+force-badtest makedumpfile/1:1.6.3-2/amd64
+force-badtest network-manager/1.10.6-2ubuntu1/amd64
+force-badtest octave-symbolic/2.6.0-3build1/i386 octave-symbolic/2.6.0-3build1/amd64 octave-symbolic/2.6.0-3build1/ppc64el octave-symbolic/2.6.0-3build1/arm64
+force-badtest snapd/2.32+18.04/i386
+force-badtest udisks2/2.7.6-3ubuntu1/s390x
+
+# passed once as a fluke
+force-badtest libanyevent-yubico-perl/0.9.3-1
+force-badtest barrnap/0.9+dfsg-1/armhf
+
+# flaky due to timeouts
+force-badtest octave-ltfat/2.2.0+dfsg-7/arm64 octave-ltfat/2.2.0+dfsg-7/armhf octave-ltfat/2.3.0+dfsg.1-1/arm64 octave-ltfat/2.3.0+dfsg.1-1/armhf
+
+# architectures not available; tests never should have passed
+force-badtest nanopolish/all/arm64 nanopolish/all/armhf nanopolish/all/ppc64el nanopolish/all/s390x
+
+# superseded by python-ldap
+force-badtest python-pyldap/all
+
+# this is seemingly always-failed from the history we can see but is reporting
+# regression at least on patch.  Hint this until it is investigated.
+force-badtest nvidia-graphics-drivers-340/all/armhf
+
+# snapd regression due to a kernel-memory leak which is now detected
+# the fix for the kernel is in flight.
+force-badtest snapd/2.32.3.2+18.04/i386 snapd/2.32.5+18.04/i386
+
+# fails to start if it cannot bind to [::]:53, which conflicts with systemd-resolved; LP: #1764327
+force-badtest gdnsd/2.3.0-1
+
+# passed once as a fluke
+force-badtest octave-zeromq/1.2.1-3/arm64
+
+# only doc package on these archs
+force-badtest pyfai/all/ppc64el pyfai/all/s390x
+
+# assumes /etc/init.d/networking
+force-badtest pcs/0.9.162-1 pcs/0.9.164-1
+
+# flaky / test timeouts
+force-badtest mercurial/4.5.3-1ubuntu2/arm64 mercurial/4.6.1-1ubuntu1/arm64
+
+# Custom kernels can never pass tests, as the right meta is not
+# included, and some of these may not even run in scalingstack These
+# are therefore false-regressions, as triggered by e.g. pciutils -- xnox
+force-badtest linux-aws/all
+force-badtest linux-azure/all
+force-badtest linux-azure-edge/all
+force-badtest linux-euclid/all
+force-badtest linux-gcp/all
+force-badtest linux-gke/all
+force-badtest linux-hwe/all
+force-badtest linux-hwe-edge/all
+force-badtest linux-oem/all
+
+# flaky test due to race with ipv6 RA due to deliberate networkd change
+force-badtest netplan.io/0.36.1
+
+# the source package for linux-image has changed and the test suite now needs updated; LP: #1766740
+force-badtest apport/2.20.9-0ubuntu6/amd64 apport/2.20.9-0ubuntu7/amd64
+
+# regressed in release due to missing python deps and changed transitive dependencies
+force-badtest snapcraft/2.42+18.04.2
+
+# package removed from release, no point in keeping it out due to 32-bit-specific autopkgtest failure
+force-badtest why/2.39-2build1/i386 why/2.39-2build1/armhf why/2.39-2build2/i386 why/2.39-2build2/armhf
+
+# searx is internally segfaulting regardless of which web-server it is used with: LP: #1772749 LP: #1772753.
+force-badtest searx/0.14.0+dfsg1-2/amd64 searx/0.14.0+dfsg1-2/i386 searx/0.14.0+dfsg1-2/s390x
+
+# Odd_Bloke: tests don't compile in release pocket, filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900367
+force-badtest xtensor-python/0.12.4-1
+
+# gings: passed accidentially once
+force-badtest pyfai/0.15.0+dfsg1-1/amd64
+
+# regressed in release, probably due to gcc/binutils
+force-badtest abi-compliance-checker/2.3-0ubuntu1/arm64 abi-compliance-checker/2.3-1/arm64
+
+# vorlon> crash in an unrelated module used only for testing
+# sil2000> The test flakiness spread from arm64 to other archs. Tracked in Debian under #902628
+force-badtest r-cran-curl/3.1-2/arm64 r-cran-curl/3.2-1/arm64
+force-badtest r-cran-curl/3.2-2build1/arm64 r-cran-curl/3.2-2build1/ppc64el r-cran-curl/3.2-2build1/s390x
 
=== added file 'ubuntu-sru'
=== added file 'vorlon'
--- vorlon	1970-01-01 00:00:00 +0000
+++ vorlon	2018-07-31 19:04:17 +0000
@@ -0,0 +1,211 @@
+# broken on arm64 with new jemalloc; skip it anyway to let the transition in.
+force-skiptest mariadb-10.1/1:10.1.29-6build2/arm64
+
+force-badtest gist/all/armhf gist/all/s390x
+force-badtest ruby-parallel/all/armhf ruby-parallel/all/s390x ruby-ferret/all/armhf
+
+# flaky due to timeouts
+force-badtest node-foreground-child/1.5.6-4ubuntu2/armhf
+
+# test failure not reproducible locally or in Debian; not worth blocking on
+force-badtest ack/2.22-1
+
+# regressed in release, possibly an infrastructure issue
+force-badtest r-cran-openssl/0.9.6-1build1/amd64
+
+# tests broken by new python-astropy; allow to regress rather than leaving the rest of astropy family broken
+force-badtest aplpy/1.1.1-1
+force-badtest gwcs/0.7-2
+force-badtest python-asdf/1.3.1-2
+# was already broken but silently passing; failure now exposed thanks to the maintainer
+force-badtest python-asdf/1.3.3-1/s390x python-asdf/2.0.1-1/s390x
+force-badtest python-asdf/2.0.1-1/armhf
+
+# possibly due to a valgrind change?
+force-badtest colord/1.3.3-2build1/ppc64el
+
+# regressed in release due to updated graphviz
+force-badtest botch/0.21-5
+
+# highly racy at best
+force-badtest node-tap/11.0.0+ds1-2/arm64
+
+# regressed with move to kvm
+force-badtest coz-profiler/0.1.0-2
+force-badtest python-docker/2.5.1-1
+
+# requires its own version of mariadb-test, that binary package now owned by mariadb-10.2.
+force-badtest mariadb-10.1/1:10.1.29-6 mariadb-10.1/1:10.1.29-6build2 mariadb-10.1/1:10.1.29-6ubuntu2
+
+# ANAIS
+force-badtest ruby-mongo/all/i386
+
+# only passes in a newer version.
+force-badtest slurm-llnl/17.02.9-1/armhf slurm-llnl/17.02.9-1/i386
+
+# failing kernel autopkgtest not caused by a no-change rebuild of gdb
+force-badtest linux/4.15.0-15.16/s390x
+
+# regressed in release
+force-badtest ruby-httpclient/2.8.3-1ubuntu1
+force-badtest ghub-plus-el/0.2.1-1/s390x
+force-badtest node-component-emitter/1.2.1-1
+force-badtest node-jed/1.1.1-1
+force-badtest node-json-parse-better-errors/1.0.1-1
+force-badtest node-package/1.0.1-1
+force-badtest node-sinon-chai/2.10.0-1
+force-badtest sax.js/1.2.4-1
+force-badtest svgpp/1.2.3+dfsg1-3ubuntu1/s390x
+force-badtest libcoap/4.1.2-1/s390x
+force-badtest rclone/1.36-3
+force-badtest bio-tradis/1.3.3+dfsg-3
+force-badtest astroscrappy/1.0.5-1build3
+force-badtest docker-libkv/0.2.1-1
+force-badtest golang-github-xordataexchange-crypt/0.0.2+git20170626.21.b2862e3-1
+force-badtest keyutils/1.5.9-9.2ubuntu1
+force-badtest octave-zeromq/1.2.1-3/s390x
+force-badtest zodb/1:3.10.7-1build1/amd64 zodb/1:3.10.7-1build1/i386
+force-badtest reel/0.6.1-4
+force-badtest golang-github-spf13-viper/1.0.0+git20171109.4dddf7c-1
+force-badtest schleuder/3.0.0~beta11-2
+force-badtest gfs2-utils/3.1.9-2ubuntu1
+force-badtest postfix/3.3.0-1/armhf
+force-badtest node-class-utils/0.3.5-1
+force-badtest node-define-property/1.0.0-1
+force-badtest node-static-extend/0.1.2-1
+
+# how does someone write a tty-related test so bad that it passes in a container and fails in a VM?
+force-badtest pinentry/1.1.0-1/s390x pinentry/1.1.0-1/arm64 pinentry/1.1.0-1/amd64 pinentry/1.1.0-1/i386 pinentry/1.1.0-1build2/arm64 pinentry/1.1.0-1build2/s390x pinentry/1.1.0-1build2/i386 pinentry/1.1.0-1build2/amd64
+
+# Was skipped in lxc, never passed in a vm, not supported on big-endian
+# https://github.com/markfasheh/ocfs2-tools/issues/22
+force-badtest ocfs2-tools/1.8.5-5ubuntu1/s390x
+
+# bad test, assumes that architecture has WiFi, urfkill, dhcp.  previously it would SKIP on s390x, now it is run in nova-kvm and is treated as a regression rather than an always-failed
+force-badtest network-manager/all/s390x
+
+# Skip tests that fail now that s390x has full VMs
+force-badtest c-icap/1:0.4.4-1/s390x
+
+# nonsensical error with new perl; allow it to regress to let perl migrate
+force-badtest libdata-dpath-perl/0.57-1
+
+# testing triggered from autodep-8: the kernel contains matching modules which causes an installation
+# failure when used with a kernel which contains them.
+force-badtest virtualbox/5.2.8-dfsg-2
+
+# passed once as a fluke
+force-badtest libanyevent-httpd-perl/0.93-5/ppc64el libanyevent-httpd-perl/all/s390x libanyevent-httpd-perl/all/armhf
+force-badtest golang-github-mwitkow-go-conntrack/0.0~git20161129.cc309e4-1
+
+# passed once as a fluke
+force-badtest mbuffer/20171011-1ubuntu1/ppc64el
+
+# regressed in release
+force-badtest nut/2.7.4-5.1ubuntu2/s390x
+force-badtest libpoe-component-client-dns-perl/1:1.054-1ubuntu1
+force-badtest libanyevent-yubico-perl/0.9.3-1/ppc64el
+force-badtest grr/3.1.0.2+dfsg-4
+force-badtest xandikos/0.0.6-2/amd64 xandikos/0.0.6-2/i386 xandikos/0.0.6-2/arm64 xandikos/0.0.6-2/ppc64el
+# hicolor-icon-theme
+force-badtest pyxdg/0.25-4
+
+# regressed in release; maybe related to resolved/netplan.
+force-badtest ifupdown/0.8.17ubuntu1/ppc64el
+
+# broken by infra; remove badtest asap - LP: #1736390
+force-badtest openvswitch/2.9.0-0ubuntu1/i386
+
+# The only test that is run is a rebuild test because the integration test doesn't work in a container; a kernel build takes 7h on armhf, the max a test is allowed to run on autopkgtest is 2h47m.  Blacklist this until further notice.
+force-badtest linux-raspi2/all linux/all/armhf
+
+# flaky
+force-badtest node-d3-timer/1.0.7-3
+force-badtest awesome/4.2-4/armhf
+force-badtest golang-github-prometheus-tsdb/0.0~git20180118.467948f-1/amd64
+
+# regressed in release
+force-badtest pdb2pqr/2.1.1+dfsg-2
+force-badtest gap-guava/3.13+ds-2
+
+# regressed in release due to compiler strictness (stderr)
+force-badtest globjects/1.1.0-2/armhf
+force-badtest mathicgb/1.0~git20170606-1/armhf
+
+# now failing with timeouts
+force-badtest haveged/1.9.1-6/armhf
+
+# pandas no longer available on armhf
+force-badtest lmfit-py/armhf/all
+
+# flaky / timeouts
+force-badtest node-tap/11.0.0+ds1-2/armhf
+# additional flaky test/spawn.js test on all archs with new nodejs
+force-badtest node-tap/11.0.0+ds1-2/i386 node-tap/11.0.0+ds1-2/ppc64el
+
+# regressed in release; possibly all due to the same cause of something updating in the perl auto test infrastructure
+force-badtest license-reconcile/0.14
+force-badtest libsoap-wsdl-perl/3.003-2
+
+# mongodb-server is not installable on armhf/i386; this tells us nothing of whether the client works
+force-badtest python-motor/all/armhf python-motor/all/i386
+
+# already broken in release
+force-badtest ddcci-driver-linux/0.3.1-2/s390x
+
+# test deps now unsatisfiable because of kde removals
+force-badtest kopete/all/ppc64el kopete/all/s390x
+force-badtest libkf5ksieve/all/ppc64el libkf5ksieve/all/s390x
+force-badtest kf5-kdepim-apps-libs/all/ppc64el kf5-kdepim-apps-libs/all/s390x
+force-badtest libkf5calendarsupport/all/ppc64el libkf5calendarsupport/all/s390x
+force-badtest libkf5incidenceeditor/all/ppc64el libkf5incidenceeditor/all/s390x
+force-badtest libkf5gravatar/all/ppc64el libkf5gravatar/all/s390x
+force-badtest libkf5mailimporter/all/ppc64el libkf5mailimporter/all/s390x
+force-badtest akonadi-calendar/all/ppc64el akonadi-calendar/all/s390x
+force-badtest libkf5eventviews/all/ppc64el libkf5eventviews/all/s390x
+force-badtest kdepim-addons/all/s390x
+force-badtest kdepim-runtime/all/ppc64el kdepim-runtime/all/s390x
+force-badtest parley/all/ppc64el parley/all/s390x
+
+# non-empty stderr with new g++
+force-badtest glbinding/2.1.1-1/armhf
+
+# passes once in a blue moon, just often enough to gum things up.
+force-badtest pyzmq/16.0.2-2build2
+
+# regressed in release by unknown means
+force-badtest qbzr/0.23.2-3/ppc64el qbzr/0.23.2-3/s390x
+
+# regressed due to new warnings from gcc
+force-badtest ciftilib/1.5.1-1build1
+
+force-badtest aptdaemon/1.1.1+bzr982-0ubuntu19
+
+# "blacklisted", self-explanatory.
+force-badtest upstart/blacklisted libnih/blacklisted linux/blacklisted/i386 linux/blacklisted/amd64 linux/blacklisted/ppc64el
+force-badtest stress-ng/blacklisted
+
+# As requested by yofel: testing needed to allow a xenial SRU.
+force-badtest plasma-framework/all/s390x
+
+# breaks with firefox 49, which (with this hint) we are allowing into the release
+force-badtest y-u-no-validate/2013052407-3
+
+# bad test, but better to have this package in xenial and unblock things than leave it on the list
+force-badtest guessit/0.11.0-2
+
+# sil2100: the ubuntu-image armhf tests are failing due to some issues with mkfs.ext4 on that arch, in-progress, hard to debug. No sense in blocking migrations (LP: #1740840)
+force-badtest ubuntu-image/1.3+18.04ubuntu2/armhf
+
+# sil2100: unreliable test-suite, we don't care about qt bindings on s390x
+force-badtest python-qtpy/1.3.1-1build1/s390x
+
+# rbalint: arm64 testbed hard-reboots breaking shutdown test LP: #1748280
+force-badtest unattended-upgrades/all/arm64
+
+# xnox: dgit fails its ADT tests with new gnupg2, filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889594.
+force-badtest dgit/4.3
+
+# Odd_Bloke: 3 tests (of 386) are failing; they are all failing because the
+# formatting of tracebacks has changed between Ruby 2.3 and 2.5
+force-badtest ruby-test-unit/3.2.5-1