[Bug 1200693] Re: copy_timeout is too short and not configurable

Launchpad Bug Tracker 1200693 at bugs.launchpad.net
Wed Oct 9 06:29:30 UTC 2013


This bug was fixed in the package autopkgtest - 2.3.7

---------------
autopkgtest (2.3.7) unstable; urgency=low


  * tests/adt-run: Factorize a base test class with common functionality.
  * lib/VirtSubproc.py, downtmp_mktemp(): Create temporary directory in the
    target (which isn't the host for anything but the null runner), to fix the
    schroot/chroot runners for directories.
  * Only show stdout/stderr in realtime if tests run in the same file system
    as the host, as otherwise we cannot create/use a named pipe. If not, fall
    back to the old way of just showing the complete stdout/stderr after the
    tests finished. (LP: #1235189)
  * Add some test cases for adt-virt-chroot.
  * Add new --timeout-copy option to make copy timeout configurable. Pass that
    down to adt-virt-* via the environment ($ADT_VIRT_COPY_TIMEOUT).
    (LP: #1200693)
  * Fix tests to also work with Python 3.1.
  * tests/testpkg: Go back to compat level 7 so that this also works on older
    Debian/Ubuntu releases.

 -- Martin Pitt <mpitt at debian.org>  Tue, 08 Oct 2013 18:55:33 +0200

** 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/1200693

Title:
  copy_timeout is too short and not configurable

Status in “autopkgtest” package in Ubuntu:
  Fix Released

Bug description:
  Version: 2.2.4

  lib/VirtSubProc.py defines copy_timeout as 300. A test run seems to
  want to copy my entire build tree multiple times, which for php5 is on
  the order of gigabytes and takes longer than this on the VM I'm using.

  In the case of php5, the build tree is around 1.7G, and adt-run
  appears to be copying this into temporary subdirectories dsc0-build,
  dsc0-tests-tree and tb-scratch. Three copies of 1.7G takes longer than
  five minutes.

  The timeout should, at the least, be configurable.  Although the CLI
  provides parameters to adjust some timeouts, it appears that this
  particular timeout cannot be adjusted.

  Workaround: change the code manually to define copy_timeout as 30000
  instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1200693/+subscriptions



More information about the foundations-bugs mailing list