Bug#850494: how to force a test that has breaks-testbed set?

Simon McVittie smcv at debian.org
Mon Jan 16 08:25:10 UTC 2017

Control: retitle 850494 should be possible to ignore test restrictions by request
Control: severity 850494 wishlist
Control: tags 850494 + patch

On Sat, 07 Jan 2017 at 08:53:13 +0100, Evgeni Golov wrote:
> the docs say:
> breaks-testbed
>     When this restriction is present the test will usually be skipped
>     unless the testbed's virtualisation arrangements are sufficiently
>     powerful, or alternatively if the user explicitly requests.
> However, I could not find any docs how to "explicitly request" this.

As far as I can see, you can't.

The attached patches add an --ignore-restrictions option compatible with
the one in sadt(1).

I would also find this facility useful when proposing new restrictions.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Check-restrictions-with-testbed-compat-not-during-in.patch
Type: text/x-diff
Size: 2589 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/autopkgtest-devel/attachments/20170116/b6321240/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Allow-restrictions-to-be-ignored-from-the-command-li.patch
Type: text/x-diff
Size: 14191 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/autopkgtest-devel/attachments/20170116/b6321240/attachment-0001.patch>

More information about the autopkgtest-devel mailing list