I pushed to try from my mozilla-aurora tree: https://tbpl.mozilla.org/?tree=Try&rev=7fc8ec0021a8 All tests failed on Android, I suspect the cause is not due to my changes but some error in the testing framework.
I filed bug 725703 to detect this and work properly. Until then, you can fix this by updating your android mozconfigs or android mozconfig-extras with ac_add_options --with-branding=mobile/android/branding/nightly (or mobile/xul/branding/nightly for android-xul). The mozconfigs are currently at mobile/android/config/mozconfigs/android/nightly and mobile/xul/config/mozconfigs/android/nightly.
The problem still occurs it seems: https://tbpl.mozilla.org/?tree=Try&rev=af0e1e41365c
(In reply to Mats Palmgren [:mats] from comment #3) > The problem still occurs it seems: > https://tbpl.mozilla.org/?tree=Try&rev=af0e1e41365c You didn't fix the mozconfigs. (In reply to Aki Sasaki [:aki] from comment #1) > I filed bug 725703 to detect this and work properly. > > Until then, you can fix this by updating your android mozconfigs or android > mozconfig-extras with ac_add_options > --with-branding=mobile/android/branding/nightly (or > mobile/xul/branding/nightly for android-xul). > > The mozconfigs are currently at > mobile/android/config/mozconfigs/android/nightly and > mobile/xul/config/mozconfigs/android/nightly.
I have a slightly sketchy looking Try run (for a patch against beta): https://tbpl.mozilla.org/?tree=Try&rev=9de38e859dfd I modified mozconfigs, hopefully in the correct way. XUL looks 100% okay, as well as Android Mochitests, but the crash and reftests are all orange. Which seems a little worse than the usual Android tests.
But in this other try run (with that same patch against Aurora), all of the native Android tests look okay, so who knows: https://tbpl.mozilla.org/?tree=Try&rev=732f5c93c0d4
> You didn't fix the mozconfigs. Yeah, I misunderstood, I thought you had fixed that other bug and wanted me to test.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Priority: P2 → --
Resolution: --- → DUPLICATE
Duplicate of bug: 725703
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.