Closed
Bug 1480546
Opened 7 years ago
Closed 7 years ago
remoteautomation does not explicitly report why it stopped waiting for an app
Categories
(Firefox for Android Graveyard :: Testing, defect, P1)
Firefox for Android Graveyard
Testing
Tracking
(firefox63 fixed)
RESOLVED
FIXED
Firefox 63
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
Attachments
(1 file)
|
682 bytes,
patch
|
bc
:
review+
|
Details | Diff | Splinter Review |
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.
|
Assignee | |
Comment 1•7 years ago
|
||
Attachment #8997145 -
Flags: review?(bob)
|
||
Comment 2•7 years 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•7 years ago
|
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
|
||
Comment 4•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
|
||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•