1569688 - geckoview 'mach mochitest' runs with e10s disabled

Status: RESOLVED FIXED

(GeckoView Graveyard :: Sandboxing, defect, P1)

Description

[Geoff Brown [:gbrown]]

In continuous automation, geckoview mochitest runs with e10s enabled, as expected. But locally, 'mach mochitest', which also uses geckoview by default now, has e10s disabled - how'd that happen?

$ mach mochitest
...
 0:17.14 adb INFO launch_application: am start -W -n org.mozilla.geckoview.test/org.mozilla.geckoview.test.TestRunnerActivity -a android.intent.action.MAIN ... --ez use_multiprocess False ...

Comment 1

[James Willcox (:snorp) ([e-mail]) (he/him)]

While that is troubling, TestRunnerActivity doesn't actually use that value, so it is in fact running with e10s.

Comment 2

[Geoff Brown [:gbrown]]

Oh, that's good!

Also, wpt, reftests and geckoview-junit are not affected (correctly run with e10s by default).

Comment 3

[Geoff Brown [:gbrown]]

Attachment: Bug 1569688 - Use e10s by default for geckoview mochitest; r=jmaher

The default, options.app == None, implies geckoview, with e10s.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/423bac18b356
Use e10s by default for geckoview mochitest; r=jmaher

Comment 5

[Cristina Coroiu [:ccoroiu]]

https://hg.mozilla.org/mozilla-central/rev/423bac18b356

Comment 6

[Chris Peterson [:cpeterson]]

69=wontfix because we don't need to uplift this test fix to GV 69 Beta.

Comment 7

[Chris Peterson [:cpeterson]]

Moving some e10s bugs to the new GeckoView::Sandboxing component.