remoteautomation does not explicitly report why it stopped waiting for an app

RESOLVED FIXED in Firefox 63

Status

()

defect
P1
normal
RESOLVED FIXED
10 months ago
10 months ago

People

(Reporter: gbrown, Assigned: gbrown)

Tracking

(Blocks 1 bug)

Trunk
Firefox 63
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox63 fixed)

Details

Attachments

(1 attachment)

Assignee

Description

10 months ago
I find the logs for problems like bug 1476635 confusing. It turns out the crash directory is missing because Firefox has not exited or crashed -- it is simply in the background. I just want to log what activity is in the foreground when our top-activity-based wait completes.

Comment 2

10 months ago
Comment on attachment 8997145 [details] [diff] [review]
in remoteautomation, log top activity after app wait completes

Review of attachment 8997145 [details] [diff] [review]:
-----------------------------------------------------------------

r+ lgtm
Attachment #8997145 - Flags: review?(bob) → review+
Assignee

Updated

10 months ago
Priority: -- → P1

Comment 3

10 months ago
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/658f019ace0e
Enhance logging for Android automation app wait; r=bc

Comment 4

10 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/658f019ace0e
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
You need to log in before you can comment on or make changes to this bug.