+++ This bug was initially created as a clone of Bug #866795 +++ We have tests running on Cedar for Android 4.0 debug builds and there is interest in running those tests on all trunk trees, but several tests fail frequently. This meta bug tracks our efforts to turn this green: https://tbpl.mozilla.org/?tree=Cedar&showall=1&jobname=android.*debug
Assignee: nobody → blassey.bugs
Bug 682129 is important here because most of the remaining failures are assertion failures, reported in the main log only as "Assertion count N is greater than expected range m-n assertions." The specific assertions have been reported in logcat, but the logcat buffer has been over-written before being dumped to the main log.
(In reply to Geoff Brown [:gbrown] from comment #1) > Bug 682129 is important here because most of the remaining failures are > assertion failures, reported in the main log only as "Assertion count N is > greater than expected range m-n assertions." The specific assertions have > been reported in logcat, but the logcat buffer has been over-written before > being dumped to the main log. Complete logcats are available now. See http://gbrownmozilla.wordpress.com/2014/02/12/complete-logcats-for-android-tests/.
No longer depends on: 682129
Android Debug test status: - mochitests (M1-M8) and js-reftests (J1-J3) are running on trunk - mochitest-gl has a consistent crash - bug 1008433 - robocop has 2 consistent crashes - bug 1008423 and bug 1008426 - crashtests have a few remaining assertion mismatches - bug 962676 - we have not yet tried to run plain-reftests, xpcshell, or cppunit tests - bug 1008373 - we would like to report assertions better - bug 1000995
Android 4.0 Debug xpcshell tests now run on trunk trees.
We hope to start running Android Debug tests soon on the 4.3 emulator and retire the corresponding Android 4.0 Debug tests. Further efforts to resolve Android debug test failures might be better applied to Android 4.3, bug 1140454.
Component: General Automation → General
Product: Release Engineering → Release Engineering
Component: General → Release Automation: Other
QA Contact: catlee → sfraser
I think we are good now.
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.