Closed Bug 1594735 Opened 2 years ago Closed 1 year ago

test-android-em-7.0-x86_64/opt-geckoview-xpcshell-e10s-1 is perma-fail under new packet deployment


(GeckoView :: General, defect, P1)



(firefox72 fixed)

Tracking Status
firefox72 --- fixed


(Reporter: wcosta, Assigned: gbrown)



(Whiteboard: [geckoview]?)


(1 file)

As Nov. 9, Taskcluster will switch deployment to firefox-ci, and machines will be upgraded to Ubuntu 18.04.

The test test-android-em-7.0-x86_64/opt-geckoview-xpcshell-e10s-1 doesn't work under this new deployment.

Component: Testing → General
Product: Firefox for Android → GeckoView

(In reply to Wander Lairson Costa [:wcosta] from comment #0)

The test test-android-em-7.0-x86_64/opt-geckoview-xpcshell-e10s-1 doesn't work under this new deployment.

That log has 2 failures:

[task 2019-11-07T14:04:18.416Z] 14:04:18 WARNING - TEST-UNEXPECTED-FAIL | dom/presentation/tests/xpcshell/test_presentation_session_transport.js | xpcshell return code: 0

[task 2019-11-07T14:09:21.400Z] 14:09:21 WARNING - TEST-UNEXPECTED-TIMEOUT | dom/presentation/tests/xpcshell/test_tcp_control_channel.js | Test timed out

Both of those tests are already failing intermittently on Android.

See Also: → 1422582, 1555323

Geoff, does this look like a GeckoView bug or a test runner or infra problem on Packet?

Flags: needinfo?(gbrown)
Whiteboard: [geckoview]?

I'm not sure where the problem is. I don't think there's reason to suspect the test runner or harness - lots of other tests seem to be running fine.

I'm tempted to say infra since the perma-fail starts with the new deployment (which incidentally is curious, since the test is running in an emulator in a docker is the host os having an effect?), but since these tests are already failing intermittently, maybe the new deployment is just changing timing or something, triggering a more persistent failure? Failures seem to be android/geckoview-specific, so maybe it's geckoview?

Flags: needinfo?(gbrown)

Today X1 is not perma-fail but does fail frequently. X2 also has a high rate of failure. Several tests seem to be involved.

Recall that the last time the android emulator was upgraded, we continued to use the older version for xpcshell because of bug 1568063.

I tried upgrading now:

and all of the failures seen in this bug seem to have disappeared. However, bug 1568063 still occurs (only 1 failure in 120 tasks in this try push).

Just a heads up that the new deployment upgrades Ubuntu from 14.04 to 18.04.

Assignee: nobody → gbrown

Upgrade the emulator used by xpcshell tests to 29.2.1, the same version used
by all other android tests.
We have delayed this upgrade because of intermittent failures seen on the new
emulator not seen previously - bug 1568063. After the upgrade to
Ubuntu 18.04, try runs with the new emulator show that bug 1568063 persists
but has less impact than the intermittent failures it resolves: More tests
pass consistently with the new emulator than with the old.

Regressions: 1568063
Pushed by
Upgrade android emulator used for x86_64 xpcshell tests; r=aerickson
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.