[tracking] Get unittests running on Android x86 [Emulator]

RESOLVED DUPLICATE of bug 891959

Status

Testing
General
RESOLVED DUPLICATE of bug 891959
5 years ago
4 years ago

People

(Reporter: bc, Assigned: dminor)

Tracking

Trunk
x86
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Tracking bug for getting unittests running on Android x86 emulators
(Assignee)

Comment 1

5 years ago
I'll be looking at this for Q2.
Assignee: nobody → dminor
Status: NEW → ASSIGNED
(Assignee)

Comment 2

5 years ago
I've spent some time running through mochitests. There are several hundred unexpected failures and also another 100 or so tests that will consistently timeout. I also see some process crashes, which I haven't diagnosed yet.

I haven't worked through all of the mochitests yet as it takes awhile to identify and remove timeout causing tests, but I'm going to try the other test harnesses to see what the situation is like there.
(Assignee)

Comment 3

5 years ago
Robocop gives an "interesting" error on startup that will require further investigation:

    I/SUTAgentAndroid( 1729): 10.0.2.2 : exec "MOZ_CRASHREPORTER=1,XPCOM_DEBUG_BREAK=stack,MOZ_HIDE_RESULTS_TABLE=1,MOZ_CRASHREPORTER_NO_REPORT=1,NO_EM_RESTART=1,MOZ_PROCESS_LOG=/tmp/tmpJvAusDpidlog,XPCOM_MEM_BLOAT_LOG=/tmp/tmpLRYM2e/runtests_leaks.log" am instrument -w -e deviceroot /mnt/sdcard/tests -e class org.mozilla.fennec_dminor.tests.testAllPagesTab org.mozilla.roboexample.test/org.mozilla.fennec_dminor.FennecInstrumentationTestRunner
    D/AndroidRuntime( 2661):
    D/AndroidRuntime( 2661): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
    D/AndroidRuntime( 2661): CheckJNI is ON
    D/dalvikvm( 2661): Trying to load lib libjavacore.so 0x0
    D/dalvikvm( 2661): Added shared lib libjavacore.so 0x0
    D/dalvikvm( 2661): Trying to load lib libnativehelper.so 0x0
    D/dalvikvm( 2661): Added shared lib libnativehelper.so 0x0
    D/AndroidRuntime( 2661): Calling main entry com.android.commands.am.Am
    D/dalvikvm( 2661): Note: class Landroid/app/ActivityManagerNative; has 156 unimplemented (abstract) methods
    W/ActivityManager( 1197): Permission Denial: startInstrumentation asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
(Reporter)

Comment 4

5 years ago
dminor, I assume this was with Android 4.2? I've seen this also in Autophone. We are planning on using mozbase's launchFennec which has a fix for this issue. See bug 838844 and bug 862508.
(Assignee)

Comment 5

5 years ago
bc, it is under Android 4.2. Thanks for the heads up.
(Assignee)

Comment 6

5 years ago
Reftests show a small number of unexpected results (20). Crashtests and JSReftests work fine.
(Assignee)

Comment 7

5 years ago
Talos tests run. tsvg, ts_paint work, tp4m runs but has problems parsing the results. trobopan (and other robocop based tests) will not work until the activity manager problem under 4.2 is resolved.
(Assignee)

Comment 8

5 years ago
The patch to deviceManagerSUT launchProcess was taken care of by bug 873628, which got the robocop tests running. Fennec crashes intermittently when running robocop and this will require more investigation.

A patch to add an androidx86.json file for mochitests was part of bug 875737, which gives a green run for mochitests in 8 chunks.

Android x86 specific known fails for reftests are being done as part of bug 875801. Some of the fails for regular Android pass on Android x86, so the platform needs to be tracked separately. Crashtests and JSRefTests work without anything special handling.

Mozharness scripts to run mochitest, robocop, reftest, jsreftest and crashtests were done as part of bug 867377 and have been landed in mozharness.

Updated

5 years ago
Depends on: 891200

Updated

5 years ago
No longer depends on: 891200
We are *still* working on this, but it is tracked in 891959 these days...
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 891959
You need to log in before you can comment on or make changes to this bug.