Closed
Bug 1092192
Opened 10 years ago
Closed 8 years ago
Disable Exchange Services on Android 4.2 x86 emulator
Categories
(Testing :: General, defect)
Tracking
(firefox53 fixed)
RESOLVED
FIXED
mozilla53
Tracking | Status | |
---|---|---|
firefox53 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
Exchange Services spew lots of messages to the logcat on the 4.2 emulator. There is concern that it might be involved in some test failures, and probably no good reason to keep it running - let's disable. https://bugzilla.mozilla.org/show_bug.cgi?id=1091955#c2 https://bugzilla.mozilla.org/show_bug.cgi?id=1091410#c3
Assignee | ||
Comment 1•10 years ago
|
||
I can probably run the emulator locally, go into Settings > Apps > all and disable Exchange Services, then use my local system image to update the one we use for tests. Is there another way? I'd prefer something I can do from a shell.
Flags: needinfo?(mark.finkle)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → gbrown
Comment 2•10 years ago
|
||
I honestly don't know. Also, I have no idea if this is really affecting tests. Only a desire to minimize other processes on the device while tests are running.
Flags: needinfo?(mark.finkle)
Comment 3•10 years ago
|
||
(In reply to Geoff Brown [:gbrown] from comment #1) > I can probably run the emulator locally, go into Settings > Apps > all and > disable Exchange Services, then use my local system image to update the one > we use for tests. Is there another way? I'd prefer something I can do from a > shell. Is it a separate package that you can uninstall?
Comment 4•10 years ago
|
||
(In reply to Nick Alexander :nalexander from comment #3) > (In reply to Geoff Brown [:gbrown] from comment #1) > > I can probably run the emulator locally, go into Settings > Apps > all and > > disable Exchange Services, then use my local system image to update the one > > we use for tests. Is there another way? I'd prefer something I can do from a > > shell. > > Is it a separate package that you can uninstall? Locally, I see chocho:gecko-dev nalexander$ adb shell pm list packages | grep exc package:com.android.exchange Not clear what that package covers and if that can be uninstalled.
Comment 5•10 years ago
|
||
(In reply to Nick Alexander :nalexander from comment #4) > (In reply to Nick Alexander :nalexander from comment #3) > > (In reply to Geoff Brown [:gbrown] from comment #1) > > > I can probably run the emulator locally, go into Settings > Apps > all and > > > disable Exchange Services, then use my local system image to update the one > > > we use for tests. Is there another way? I'd prefer something I can do from a > > > shell. > > > > Is it a separate package that you can uninstall? > > Locally, I see > > chocho:gecko-dev nalexander$ adb shell pm list packages | grep exc > package:com.android.exchange > > Not clear what that package covers and if that can be uninstalled. According to the Totally Authoritative http://blog.burrowsapps.com/2014/03/what-android-apps-are-safe-to-remove.html (a site that I just googled), com.android.exchange can be uninstalled safely.
Assignee | ||
Comment 6•10 years ago
|
||
$ adb uninstall com.android.exchange Failure $ adb shell root@android:/ # pm uninstall com.android.exchange Failure root@android:/ # Disabling in app settings seems to work okay.
Assignee | ||
Comment 7•9 years ago
|
||
We only run xpcshell tests on x86 now, and they have been running very reliably, so I am reluctant to make any changes now.
Assignee: gbrown → nobody
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → gbrown
Assignee | ||
Comment 8•8 years ago
|
||
This may be implicated in dumpsys timeouts seen in experimental mochitest-chrome tests - bug 1315749.
Pushed by gbrown@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/9df2b4f740d7 Update Android x86 AVD; r=me
Comment 10•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/9df2b4f740d7
Status: REOPENED → RESOLVED
Closed: 9 years ago → 8 years ago
status-firefox53:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
You need to log in
before you can comment on or make changes to this bug.
Description
•