Bug#851558: autopkgtest: define Restrictions for tests that aren't suitable for gating CI
elbrus at debian.org
Mon Jan 16 20:53:22 UTC 2017
On 16-01-17 12:34, Martin Pitt wrote:
> Simon McVittie [2017-01-16 9:06 +0000]:
>> Specifically, if a maintainer is unable to fix a particular unreliable
>> or broken test, or the non-RC bug that it exposes, I think it's still
>> correct for that test to continue to run on CI infrastructure, with
>> its result logged but the usual side-effects of that result ignored.
> FTR, in Ubuntu (same as in the discussion going on for adopting this into
> Debian) we use britney overrides for this, like in
> i. e. the tests still run, but britney won't block the package on its failure.
Can this be done on a per test basis, or only on a per package basis? I
think there is need for this to (also) work on the former.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: OpenPGP digital signature
More information about the autopkgtest-devel