1219342 - Enable e10s tests on mozilla-beta when Gecko 43 is uplifted to it

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Erin Lancaster [:elan]]

e10s tests are enabled for Nightly and Aurora and now we need them on Beta.

Comment 1

[Jim Mathies [:jimm]]

We need to figure out what needs to happen here, specifically:

1) what suites are we turning on
2) patches for turning them on
3) we should run beta43 through try + e10s test before we do this in production

related bug: Bug 1218475 - Opt-In Enable e10s for Firefox 43.0 Beta

Comment 2

[Ryan VanderMeulen [:RyanVM]]

My main concern here is that prior experience with uplift simulation Try pushes (which mostly end up affecting the NIGHTLY_BUILD/RELEASE_BUILD ifdefs) is that e10s tests do not respond well to attempting to run on channels they aren't meant to be.

I'm worried that if we enable these tests, we're going to have a pile of orange waiting for us since nothing is changing from an ifdef standpoint.

Comment 3

[Ryan VanderMeulen [:RyanVM]]

Attachment: enable e10s tests on Beta

This patch should do the trick from the buildbot side of things. A builder diff shows the expected results.

As Jim said, this can't land until we've verified that things are green on Try. My expectation is that currently, they won't be. After tomorrow's uplift, pushing m-b to Try directly should suffice for testing, however.

Comment 4

[Jonathan Howard]

bug 1226487 enabled for A/B beta test.
Noticed app.update.channel is default on basic treeheader beta build, i.e. e10s disabled. Something probably needs changing when this bug is dealt with.

Comment 5

[Chris Peterson [:cpeterson]]

Ryan, do we still need to uplift e10s tests to mozilla-beta? Is this bug still relevant?

Comment 6

[Ryan VanderMeulen [:RyanVM]]

No, this is long-done.