1305124 - Start running mochitest-a11y with e10s enabled in automation

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Ryan VanderMeulen [:RyanVM]]

Now that Aaron is getting close to getting e10s a11y support ready for widespread testing, we need to get automated tests running in automation.

Explicit non-goal for this bug: splitting up non-e10s mochitest-other across all platforms. We should probably consider doing that soon to avoid confusion, but we can take care of this bug without having to do that.

Comment 1

[Ryan VanderMeulen [:RyanVM]]

To the people CCed: feel free to add any other deps you want.

Comment 2

[Ryan VanderMeulen [:RyanVM]]

Getting this running on Taskcluster is apparently trivial. So that's awesome.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=2e09e0469bf62bafe4b72e7bef3f1c6092072ff7

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

except that is linux only- but a start!

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Yeah, good enough for ensuring that they're not completely and utterly broken before I embark on the buildbot end of things.

Comment 5

[David Bolter [:davidb] (NeedInfo me for attention)]

Ryan, is there anything for my team to do here?

Comment 6

[Ryan VanderMeulen [:RyanVM]]

This got held up a bit by questions about how useful M-e10s(a11y) would actually be. I'll try to work on it soon, though.

Comment 7

[Ryan VanderMeulen [:RyanVM]]

Finally got Linux working with some hacks. And they're currently busted.
https://treeherder.mozilla.org/logviewer.html#?job_id=29806780&repo=try

Though I'm still a bit confused about what I'm seeing in the logs. As expected, the beginning of the run shows "runtests.py | Running with e10s: True" in the logs, but at the end of the run, I still see "INFO Mode: non-e10s". Not entirely sure what to make of that :\

Comment 8

[Ryan VanderMeulen [:RyanVM]]

After a number of discussions with various accessibility people, the unanimous conclusion is that there isn't any value in trying to stand up M-e10s(a11y). It won't effectively test cross-process things anyway and time is better-spent on adding more browser-chrome tests to the ones that are already there.