autopkgtest 3.20git1 source package in Ubuntu


autopkgtest (3.20git1) xenial; urgency=medium

  * When testing click packages, don't regenerate all AppArmor profiles if
    /var/cache/apparmor/click-ap.rules already exists. That way the profiles
    can be pre-adjusted once in a testbed instead of once for each test run,
    which greatly speeds up iterations. (LP: #1553797)
  * Move SshRunner* tests from lxc to lxd.
  * NullRunner.test_tree_output_dir test: Only check for cpu_{model,flags} on
    x86 and ARM, as these need parsing adjustments on other architectures.
  * Only run lxd autopkgtest on x86 architectures, as does not have much else.

 -- Martin Pitt <email address hidden>  Mon, 14 Mar 2016 09:19:17 +0100

Upload details

Uploaded by:
Martin Pitt on 2016-03-14
Uploaded to:
Original maintainer:
Autopkgtest team
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section


Xenial: [FULLYBUILT] amd64


File Size SHA-256 Checksum
autopkgtest_3.20git1.tar.xz 154.1 KiB b3b68b996e64e837cd0c05a6d8eec4cfa6420a276fb0e08ca495df13067fa16d
autopkgtest_3.20git1.dsc 1.8 KiB 5d62d16a83bf92af22f3055b9d5febcce215a46ac9a2e4282302a4312839d274

Available diffs

View changes file

Binary packages built by this source

autopkgtest: automatic as-installed testing for Debian packages

 autopkgtest runs tests on binary packages. The tests are run on the
 package as installed on a testbed system (which may be found via a
 virtualisation or containment system). The tests are expected to be
 supplied in the corresponding Debian source package.
 See adt-run(1) and /usr/share/doc/autopkgtest.
 Depending on which virtualization server you want to use, you need to
 install additional packages (schroot, lxc, lxd, or qemu-system)
 For generating tests of well-known source packages such as Perl and Ruby
 libraries you should install the autodep8 package.