[Bug 1183916] Re: Purge build dependencies after building package

[Robie Basak]

I think autopkgtest is working as designed. Since run-adt-test uses the
adt-virt-null driver, and the adt-virt-null driver doesn't support the
"revert" virt driver capability, build dependencies do not get cleaned
up. To fix this, run-adt-test should use a proper virt driver that
supports "revert" and "revert-full-system".

Cleaning up build dependencies when using virt drivers that do support
"revert-full-system" will just waste time, though I don't see it doing
any harm. So I'm neutral on Adam's approach, although I think it's just
a workaround for problem caused by the consequence of using adt-virt-
null in production.

-- 
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/1183916

Title:
  Purge build dependencies after building package

Status in Automated Testing of Ubuntu Packages:
  Confirmed
Status in “autopkgtest” package in Ubuntu:
  Triaged

Bug description:
  Adding autopkgtests to bzr-git, I ran into an issue.

  I did tested my changes locally using using lp:auto-package-testing.

  .bin/run-adt-test -S file:///home/asb/development/pkg-bzr/bzr-git

  Log attached...

  The tests were successful. After uploading to Debian and syncing to
  Ubuntu, the test failed due to a dependency problem on Ubuntu's
  jenkins instance:

  https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-
  adt-bzr-git/1/

   Apparently, if you run it on an unpacked source tree, it builds the
  package installing all the build dependencies. It then installs the
  built binary and runs the tests without purging the build
  dependencies. This is not what I would think the expected result would
  be. I think it would make sense to purge the build dependencies after
  building package.

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