Public bug reported:
There are a whole raft of SRUs that are stuck with autopkgtest failures
on s390x. On inspection, these have all been cases where a test was
previously skipped due to the test-bed not supporting machine-isolation
that are now run because our s390x test-bed now supports VMs.
I've been marking such failures as “badtest foo/all/s390x”, but that
seems like a hammer of unnecessary size.
*Ideally* brittney/the dep8 runner would notice “All the tests which
used to pass still pass, but a test which used to be skipped is now run,
but fails” and count it as a success.
Alternatively, being able to override part of the test-suite as badtest
(badtest foo/machine-isolation/s390x or something).
Alternatively, being able to re-mark a test as always-failed.
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747791
Title:
Better support autopkgtests which fail due to increased testbed
feature support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1747791/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
