Closed Bug 977635 Opened 12 years ago Closed 10 years ago

emulator.py should immediately detect if gecko stopped running

Categories

(Remote Protocol :: Marionette, defect)

Product:
Remote Protocol
Component:
Marionette
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: ahal, Unassigned)

References

Details

At the moment if a crash occurs in gecko, the emulator will continue running until the mozharness/buildbot timeout happens. Instead, we should have some mechanism to detect when gecko is no longer running and trigger some kind of event that can be processed by the harness.
Usually the emulator is closed when the related class is destroyed...I think we just need to make sure this is happening correctly.
Yes, this was more about being notified right away rather than waiting for an output timeout. Harnesses that use B2GRunner already have this ability because we wrap the adb shell /system/b2g call in a mozprocess instance. But harnesses that don't rely on restarting the b2g process like marionette-webapi or gaia-ui, need to depend on a timeout. I guess it isn't super high priority, but I think it would be nice if we could just handle gecko crashes right away. This will probably stay on the back burner for awhile.
Closing as emulator tests are no longer run because of bug 1149887
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.