I just want to add that, if debug+opt builds are too slow, we don't have to leave it at that. I think it's likely that we could tune our debug+opt builds to be much faster than they currently are; someone just needs to profile.
On Mon, Jul 29, 2013 at 5:46 PM, L. David Baron <[email protected]> wrote: > There have been some problems recently that could have been avoided > if we'd been running automated tests for Firefox OS on debug builds, > which we aren't currently doing on https://tbpl.mozilla.org/ . > > I think the important characteristic here that we need is that we > need to test builds compiled with -DDEBUG. It doesn't matter if the > builds are optimized or not (given that I'm under the impression > that running non-optimized B2G is unacceptably slow) and I'd think > we don't want debug symbols to be part of the binaries on the device > (which is a characteristic of debug builds on desktop, though I'd > hope that the build system already does something reasonable here). > > I wrote a blog post explaining more generally why I think this is > important: http://dbaron.org/log/20130729-debug-builds > > Are there plans to have B2G automated tests running on debug builds? > What's the status, and what's in the way of it happening? > > -David > > -- > 𝄞 L. David Baron http://dbaron.org/ 𝄂 > 𝄢 Mozilla http://www.mozilla.org/ 𝄂 > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
