[Bug 1414939] Re: adt wait-for-device doesn't timeout in a reboot test

[Launchpad Bug Tracker]

This bug was fixed in the package autopkgtest - 3.9.3git1

---------------
autopkgtest (3.9.3git1) vivid; urgency=medium

  * Recognize modern "Package-Type:" control field in addition to
    XC-Package-Type.
  * ssh-setup/adb: Guard adb wait-for-device with a 5 min timeout.
    (LP: #1414939)
 -- Martin Pitt <martin.pitt at ubuntu.com>   Tue, 27 Jan 2015 13:21:44 +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/1414939

Title:
  adt wait-for-device doesn't timeout in a reboot test

Status in autopkgtest package in Ubuntu:
  Fix Released

Bug description:
  From fginther:

  Experimenting with a test known to fail the reboot on the phone, 'apt-
  get remove -y --force-yes lxc'.

  adt-run does not timeout by default in a short enough time period.
  Experimenting now with setting specific values:

      --timeout-test=300 : adt-run did not abort after running for 18
  minutes. Possibly the reboot is not considered during the timeout?

  So it appears that adt-run is using 'adb wait-for-device' after a
  reboot to wait for the device to come up (see ssh-setup/adb
  wait_booted()).

  There is no timeout around this and I don't see one at any of the
  callers (but I could be missing it).

   Short term solution is to use 'timeout 600 adt-run ...'

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