On 14-04-07 08:49 PM, Ehsan Akhgari wrote:
On 2014-04-07, 8:03 PM, Robert O'Callahan wrote:
When you say "debug", you mean the emulator is running a FirefoxOS debug
build, not that the emulator itself is built debug --- right?
Given that, is it a correct summary to say that the problem is that the
emulator is just too slow?
Applying time dilation might make tests green but we'd be left with the
problem of the tests still taking a long time to run.
Maybe we should identify a subset of the tests that are more likely to
suffer B2G-specific breaking and only run those?
Do we disable all compiler optimizations for those debug builds? Can
we turn them on, let's say, build with --enable-optimize and
--enable-debug which gives us a -O2 optimized debug build?
In my experience running tests locally, a single mochitest run on the
ARM emulator (hardware: Thinkpad X220, 16GB RAM, SSD) where everything
was built with 'B2G_DEBUG=0 B2G_NOOPT=0' will run in 2 to 3 minutes. The
same test, run with 'B2G_DEBUG=1 B2G_NOOPT=0' will take 7 to 10 minutes.
--m.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
