Closed Bug 812190 Opened 12 years ago Closed 11 years ago

Figure out which events we need to wait for when restarting the B2G process

Categories

(Remote Protocol :: Marionette, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ahal, Unassigned)

Details

We've had all kinds of timeouts when restarting the b2g process in emulators, e.g: adb shell stop b2g adb shell start b2g To get around this in the short term we've had to use sleeps :( ... See: https://hg.mozilla.org/integration/mozilla-inbound/rev/473d3748d994 http://mxr.mozilla.org/mozilla-central/source/build/mobile/b2gautomation.py#171 Instead we should figure out why this is happening and what event we need to be waiting for (checking for process existence doesn't work).
I'm beginning to think this is a problem with B2G on the emulator, and not a problem in which we don't wait long enough between stopping and starting b2g. We see a similar situation on the pandas, but I haven't noticed this on an unagi/otoro.
This seems to be working reliably.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.