We're currently running a very limited set of tests on debug builds on
mozilla-b2g18.
We'd like to run a larger set on m-c. We've had them running on cedar
for some while, but the tests have been failing ever since they were
first enabled due to various problems that would likely require
developer involvement to fix.
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.
Jonathan
On 7/29/2013 5:46 PM, L. David Baron 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
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
