Closed Bug 840182 Opened 11 years ago Closed 9 years ago

Need to detect when app crashes/freezes when running marionette tests

Categories

(Remote Protocol :: Marionette, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mdas, Unassigned)

References

Details

(Keywords: pi-marionette-runner, Whiteboard: [runner])

When running tests against gaia in b2g, apps can either crash or hang, and we're stuck sending back ScriptTimeout or other unhelpful messages. It would be great if we could detect a hang/crash and then restart b2g in that case.

I spoke with cjones, and for detecting crashes, we can look for dumps in /data/b2g/mozilla/Crash Reports/, and /data/b2g/mozilla/Crash Reports/pending for pending crash logs, but jgriffin has seen that crashes don't always leave crash logs. Cjones also mentioned that we could listen for mozbrowsererror events, where crashes fall under 'fatal' errors.

As for freezes, there isn't any clear way to do that, but cjones suggests hiding the frame (setVisible(false)), then add a nextpaint listener and unhide it. We can try this approach and see if it works.
Whiteboard: [runner]
We do have this capability now in general; we can file bugs for more specific problems as needed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.