Closed Bug 1566957 Opened 4 months ago Closed 4 months ago

mozharness fails to run robocop with --disable-e10s

Categories

(Firefox for Android :: Testing, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
Firefox 70
Tracking Status
firefox-esr68 --- fixed
firefox69 --- fixed
firefox70 --- fixed

People

(Reporter: gbrown, Assigned: gbrown)

References

Details

Attachments

(1 file)

robocop always runs fennec, which should always be non-e10s. Since e10s is the default for mochitests, runrobocop.py will see options.e10s==True unless called with --disable-e10s. mach calls runrobocop with --disable-e10s, but mozharness does not. Internal defaults and assumptions ensure that most settings are non-e10s anyway, but pref browser.tabs.remote.autostart will be set incorrectly unless --disable-e10s is passed to runrobocop.py.

I think we've been running robocop in this crazy half-e10s state for months, but this recently caused trouble and confusion in bug 1565794.

Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/89da8a8fed0d
Ensure robocop runs with --disable-e10s; r=jmaher
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70
You need to log in before you can comment on or make changes to this bug.