1036793 - Jetpack e10s tests will be permaorange when mozilla-central merges to mozilla-aurora on July 21st

Status: RESOLVED FIXED

(Add-on SDK Graveyard :: General, defect)

Description

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=43495703&full=1&branch=try#error0

You can look at the (hidden, permaorange, totally failing) mochitest-e10s runs on the current aurora to see just how little you want to have to do with testing e10s on non-nightly. It doesn't work. You've got 11 days to permaorange.

Comment 1

[Dave Townsend [:mossop]]

Is e10s off on aurora or something? We should probably just disable these tests there.

Comment 2

[Tomislav Jovanovic :zombie]

i'm yet to fully investigate this, but this is somewhat odd. 

despite the name, there is nothing really "e10s" about those tests. they are our normal tab tests, only run inside a firefox instance that has the `browser.tabs.remote.autostart` pref set to true in the profile.

if e10s is disabled on aurora, the only thing that would happen is that the test tabs are not open in the content process, but that shouldn't matter at all!

Comment 3

[Phil Ringnalda (:philor)]

Yes, as bug 1002800 comment 0 puts it, "parts of e10s are enabled only on nightly".

Comment 4

[Tomislav Jovanovic :zombie]

that comment is 2+ months old, things might have changed.. i'm asking around.

Phil, what is that try run that you posted above? did you try a build that is configured as aurora?

> You can look at the (hidden, permaorange, totally failing) mochitest-e10s
> runs on the current aurora 

true, but "current aurora" presumably does not the same fixes as "current nightly" (future aurora in two weeks). and those jetpack tests have been running pretty green for 3 days now (~50 test runs, ~500 test jobs) on fx-team:

https://tbpl.mozilla.org/?tree=Fx-Team&showall=1&jobname=jetpack

Comment 5

[Phil Ringnalda (:philor)]

Top of tbpl logs there's a "for push 9ee75661140c" link that takes you to https://tbpl.mozilla.org/?rev=9ee75661140c&tree=Try where you can see the stack of patches on top of current mozilla-central which mimic the changes it gets when it's merged to aurora, yes. They run fine on fx-team because on fx-team you have a version number that ends in a2, so nightly-only features are enabled. Part of the merge to aurora changes that to ending in a1, which turns off nightly-only features, and the burning starts.

Comment 6

[Tomislav Jovanovic :zombie]

hey Phil, thanks for your patience and explanation! ;)

Comment 7

[Tomislav Jovanovic :zombie]

Attachment: Link to Github pull-request: https://github.com/mozilla/addon-sdk/pull/1545

Comment 8

[[github robot]]

Commits pushed to master at https://github.com/mozilla/addon-sdk

https://github.com/mozilla/addon-sdk/commit/07002368cccadca4056954799deadaf280fbd85f
bug 1036793 - disable e10s tests on aurora

https://github.com/mozilla/addon-sdk/commit/6ea50f603d04bc17d116f81b4249a748fb019b73
Merge pull request #1545 from zombie/1036793-e10s-aurora

bug 1036793 - disable e10s tests on aurora, r=@erikvold

Comment 9

[Dave Townsend [:mossop]]

So is this fixed now?

Comment 10

[Tomislav Jovanovic :zombie]

yes, i believe so.. i was waiting for the uplift which got delayed, and is now done in bug 1037374.