[Bug 1503150] Re: Minimize installed packages from -proposed

[Launchpad Bug Tracker]

This bug was fixed in the package autopkgtest - 3.18

---------------
autopkgtest (3.18) unstable; urgency=medium

  Behaviour changes/improvements:
  * adt-virt-lxc: Drop --eatmydata option. Conceptually this isn't specific to
    the LXC runner, it should always be used for package installation (when
    available) with all runners, but never for tests.
  * setup-commands/cloud-vm-setup, tools/adt-setup-vm: Install and use
    eatmydata.
  * Use eatmydata for --apt-upgrade and installing test dependencies, if
    available.
  * ssh-setup/nova: Provide custom implementation of "wait-reboot" using "nova
    reboot --poll". This works more reliably on some clouds.
  * ssh-setup/nova: Call "nova boot" with --debug to better be able to
    diagnose failures.
  * Extend --apt-pocket=POCKET option to accept an additional
    "=pkgname1,src:srcname1,..." package list. An entry "src:srcname" expands
    to all binary packages built by that source. If given, set up apt pinning
    to use only those packages from POCKET, so that package updates in that
    pocket can be tested independently from each other for better isolation.
    (LP: #1503150)
  * Add ssh-setup/maas: Acquire and Deploy a machine via MAAS to use as an
    autopkgtest testbed. It assumes that MaaS is already set up, machines are
    commissioned to it, and you added your ssh key to it.

  Bug fixes:
  * ssh-setup/nova: Drop "Warning: PoC", we've been using this in production
    for a long time.
  * tools/adt-setup-vm: Check if we already have a configuration for the
    specific network interface that we are configuring, not just any
    interface.
  * tools/adt-buildvm-ubuntu-cloud: Counter-hack the Ubuntu livecd-rootfs
    workaround for LP #1510345 by creating a configuration for ens3 and
    removing the one for eth0.

 -- Martin Pitt <mpitt at debian.org>  Wed, 11 Nov 2015 10:11:48 +0100

** Changed in: autopkgtest (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1503150

Title:
  Minimize installed packages from -proposed

Status in Auto Package Testing:
  Fix Released
Status in britney:
  Fix Released
Status in autopkgtest package in Ubuntu:
  Fix Released

Bug description:
  It sometimes happens that a package P in -proposed gets stuck because
  one of its dependencies D also gets uploaded and is broken. Right now
  we always run all tests against the entirety of -proposed, which will
  cause P's tests to  fail due to the broken D.

  However, in many cases P's dependencies will be satisfiable in
  -release, so if we would run tests only against P's -proposed binaries
  and only use those packages from -proposed which are necessary to
  satisfy the dependencies (to catch library transitions or packages
  with versioned Depends: which need to land in lockstep) we could land
  P and still keep D in -proposed.

  This needs fleshing out, and we need to figure out how to do that with
  apt pinning.

  Once we do that, we need to become strict in britney about always
  respecting the recorded triggering package in the result logs. We must
  then not consider newer test results which were run against a
  different trigger Q as an updated test result for a failing test
  against P. We currently only do this results-per-trigger tracking for
  kernels, but not for normal packages as the triggering package
  currently doesn't influence the test results there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1503150/+subscriptions