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

[Martin Pitt]

I (locally) ran this for a few packages in current xenial-proposed,
found/fixed one more bug, and this looks good now.

britney change to request one test per trigger:
http://bazaar.launchpad.net/~ubuntu-
release/britney/britney2-ubuntu/revision/525

autopkgtest-cloud worker change to select triggering package from
-proposed and use the rest from -release: https://git.launchpad.net
/~ubuntu-release/+git/autopkgtest-cloud/commit/?id=f4fa3badf7a

** Changed in: britney
       Status: Fix Committed => Fix Released

** Changed in: auto-package-testing
       Status: Triaged => 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 Committed

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