adt wait-for-device doesn't timeout in a reboot test
Bug #1414939 reported by
Vincent Ladeuil
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| autopkgtest (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
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-
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 ...'
| Changed in autopkgtest (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Martin Pitt (pitti) |
Revision history for this message
| Martin Pitt (pitti) wrote | #1 |
| Changed in autopkgtest (Ubuntu): | |
| assignee: | Martin Pitt (pitti) → nobody |
| status: | In Progress → Fix Committed |
| assignee: | nobody → Martin Pitt (pitti) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in autopkgtest (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed: http://