Thanks! I guess if I'm going to ask for help, I should provide information
to help people who might be interested in looking at this. We have an uber
tracking bug for test failures [1] with various sub-bugs for specific areas.
Not all test failures are covered here though, it's probably simpler to just
dig into existing failures. For that we have holly [2] set up with e10s
forced on which we do regular mc merges to. You can do the same for try
pushes by modifying mochitest harness flags in your pushes. [3] We currently
don't have bugs filed on auditing blacklisted tests yet, but a good place to
start there would be manifests in toolkit and in
browser/base/content/test/(general).
Jim
[1]
https://bugzilla.mozilla.org/showdependencytree.cgi?id=984139&hide_resolved=1
[2] https://tbpl.mozilla.org/?tree=Holly
[3]
http://mxr.mozilla.org/projects-central/source/holly/testing/config/mozharness/
-----Original Message-----
From: Gavin Sharp
Sent: Tuesday, August 26, 2014 3:04 PM
To: Jim Mathies
Cc: dev-platform
Subject: Re: Please help test e10s
I spoke to Mark Hammond about this yesterday. Mark has done some work
getting the browser-chrome tests running (bug 932142), but that work
was put aside for the FxA-Sync-in-29 push earlier this year. We have a
work week next week, we'll try to figure out how he can best help
broaden test coverage for e10s.
Gavin
On Tue, Aug 26, 2014 at 10:10 AM, Jim Mathies <jmath...@mozilla.com>
wrote:
>
> "Ryan VanderMeulen" <rya...@gmail.com> wrote in message
> news:<y4-dnfcho4l2cghonz2dnuvz_hcdn...@mozilla.org>...
>
>> I won't lie, I'm quite hesitant to dogfood something that has no
>> automated test coverage on my platform. And looking at Holly, I'm
not
>> entirely sure
>> *why* m-e10s isn't enabled for Win7/Win8 opt.
>
>
> I've been trying to get those last few mochitest-plain win tests
> cleaned up so we can. Test coverage isn't blocking our Milestone 2
> (Oct 14th) so it isn't a priority right now. But we are trying to fit
> in work on these where we can. We'd like to get plain and browser
> chrome running on trunk repos on all three platforms as soon as
> possible. We also need to audit all the blacklisting that's been done
> since some tests can probably run now that didn't, and others which
> fail are good indicators of features that aren't e10s compatible yet.
>
> If anyone has any spare cycles, we sure would love the help working
on
> tests. :)
>
> Jim
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
