[Bug 1200693] [NEW] copy_timeout is too short and not configurable

[Robie Basak]

Public bug reported:

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.

** Affects: autopkgtest (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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:
  New

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