On 7/29/2013 11:41 PM, L. David Baron wrote:
On Monday 2013-07-29 18:03 -0700, Jonathan Griffin wrote:
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.
If somebody puts in the work to get one of the test runs working
(say, mochitest-3), how quickly could we have that test running on
all branches so that it doesn't get regressed?
Very quickly...like a day or two. It just requires some changes to the
buildbot scheduling and then a buildbot reconfig.
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.
-David
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
