[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Package: autopkgtest
Version: 4.2.2
Severity: minor
Tags: upstream


the docs say:

    The test, when run, is liable to break the testbed system. This
    includes causing data loss, causing services that the machine is
    running to malfunction, or permanently disabling services; it does
    not include causing services on the machine to temporarily fail.

    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.

Background: I am running the tests inside a docker container (on
travis-ci.org, via travis.debian.net) and that gets thrown away after
the tests anyways.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages autopkgtest depends on:
ii  apt-utils       1.4~beta3
ii  libdpkg-perl    1.18.18
ii  procps          2:3.3.12-3
ii  python3         3.5.1-4
ii  python3-debian  0.1.29

Versions of packages autopkgtest recommends:
ii  autodep8  0.8

Versions of packages autopkgtest suggests:
ii  lxc          1:2.0.6-1
pn  lxd-client   <none>
ii  qemu-system  1:2.8+dfsg-1
ii  qemu-utils   1:2.8+dfsg-1
ii  schroot      1.6.10-2+b2

-- no debconf information

Reply to: