On Tue, Mar 24, 2015 at 6:40 PM, Jonathan Griffin
wrote:
> Most (or all) of the tests in that directory were not working on B2G as
> written. They were timing out and causing the harness to abort. So I
> disabled that entire directory in the interests of getting the job running.
>
> I haven't
Hi Panos,
Most (or all) of the tests in that directory were not working on B2G as
written. They were timing out and causing the harness to abort. So I
disabled that entire directory in the interests of getting the job running.
I haven't debugged any of those, but you could remove that line fro
This is very cool, I've been waiting for this for a long time!
I see that existing tests are now skipped by default on b2g, e.g.:
https://dxr.mozilla.org/mozilla-central/source/toolkit/devtools/server/tests/mochitest/chrome.ini#2
Is this because nobody has tested whether they work yet, or is it
Thanks to gbrown for doing a lot of the hard work here!
Jonathan
On Mon, Mar 23, 2015 at 4:59 PM, Bobby Holley wrote:
> Awesome - thank you for making that happen!
>
> All - if you find yourself using SpecialPowers.wrap for anything other
> than twiddling an occasional value or knob, you're doi
Awesome - thank you for making that happen!
All - if you find yourself using SpecialPowers.wrap for anything other than
twiddling an occasional value or knob, you're doing it wrong. Write a
mochitest-chrome test instead.
bholley
On Mon, Mar 23, 2015 at 4:38 PM, Jonathan Griffin
wrote:
> A moch
A mochitest-chrome job is now running on B2G emulators, and appears in
Treeherder as M(c). This job skips most existing chrome tests, since most
of the existing tests are not compatible with B2G. But it provides a
better alternative when writing mochitests that need chrome privileges than
using S
6 matches
Mail list logo
