On 2013-07-30 12:35 PM, Jonathan Griffin wrote:
More recently, the tests seem to have fallen over due to
infrastructure issues. I've filed a bug to fix the infrastructure
issues (https://bugzilla.mozilla.org/show_bug.cgi?id=899392); after
this is fixed we'll be in a better position to determine how much
work will be needed in order to stabilize the tests on debug builds.
Why are debug builds behaving so differently from non-debug? Are
they non-optimized?
Yes, they're non-optimized.
That's not true on desktop and Android, see
<https://groups.google.com/forum/#!topic/mozilla.dev.platform/4RkMpXKOcu8>
and <https://bugzilla.mozilla.org/show_bug.cgi?id=669953>. We should
absolutely consider optimizing the b2g debug builds as well. Looking at
<http://mxr.mozilla.org/mozilla-central/source/b2g/config/mozconfigs/ics_armv7a_gecko/debug>
(is that the right mozconfig?) we do in fact build with optimizations
turned on.
The reason that debug builds take much longer are the runtime checks
that we perform, and also the lower optimization level (-O1 in debug
versus -O2 in non-debug.) We might be able to experiment with building
with -O2 on b2g debug builds.
Cheers,
Ehsan
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
