Closed Bug 1480546 Opened 2 years ago Closed 2 years ago

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

Categories

(Firefox for Android :: Testing, defect, P1)

defect

Tracking

()

RESOLVED FIXED
Firefox 63
Tracking Status
firefox63 --- fixed

People

(Reporter: gbrown, Assigned: gbrown)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

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 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+
Priority: -- → P1
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/658f019ace0e
Enhance logging for Android automation app wait; r=bc
https://hg.mozilla.org/mozilla-central/rev/658f019ace0e
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
You need to log in before you can comment on or make changes to this bug.