Fennec robocop5 tests on fx-team failed with https://tbpl.mozilla.org/php/getParsedLog.php?id=35381340&tree=Fx-Team and I then retriggered it and it failed the same way again ( https://tbpl.mozilla.org/php/getParsedLog.php?id=35383311&tree=Fx-Team ). In the following push to fx-team, rc5 failed with https://tbpl.mozilla.org/php/getParsedLog.php?id=35384113&tree=Fx-Team Chat log from #fx-team for posterity: [17:58] <KWierso> rnewman: could https://tbpl.mozilla.org/php/getParsedLog.php?id=35381340&tree=Fx-Team have been caused by you in bug 969637? <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=969637 cri, --, Firefox 30, rnewman, ASSI, Regression: Crash java.lang.NullPointerException in org.mozilla.gecko.GeckoConnectivityReceiver.star <KWierso> happened twice on that push [18:00] <rnewman> KWierso: let me look [18:01] KWierso: no, doesn't look relevant; the HomePager is successfully loading, and the changes I made should cause catastrophic problems, not partial display of about:home [18:02] KWierso: but bnicholson's push beforehand could conceivably affect this <KWierso> rnewman: a later push failed with https://tbpl.mozilla.org/php/getParsedLog.php?id=35384113&tree=Fx-Team [18:03] <rnewman> looks like someone's been fiddling with the toolbar [18:04] let me see if I can reproduce [18:09] KWierso: test doesn't fail locally, even though it takes a comparable amount of time to run tried twice <KWierso> hrm <rnewman> but that bug is super weird it's launching a Yahoo search for about:home! rather than loading about:home [18:10] <KWierso> awesomebar fail or something? [18:11] <rnewman> or a mis-tap? [18:12] if you were trying to tap a Top Sites entry, or a bookmark, but about:home were in the edit field, you'd hit Yahoo so this might be a failure to leave edit mode

Various related intermittents: * Waiting for BOOKMARKS: bug 947550 * Toolbar is Yahoo/Wiki/etc.: bug 952046

bug 962103 caused this and has since been backed out (see bug 962103 comment 28 and bug 947550 comment 114 for the intermittent investigation). bug 947550 (Waiting for BOOKMARKS) should remain fixed and bug 952046 is open for the Yahoo search issue.

This still failing frequently. I've disabled the test for now. https://hg.mozilla.org/integration/mozilla-inbound/rev/6a5325cc4c91

(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #13) > This still failing frequently. I've disabled the test for now. > > https://hg.mozilla.org/integration/mozilla-inbound/rev/6a5325cc4c91 The backout hadn't merged; I don't think this needs to be disabled?

It was dying on inbound. On your backout no less.

Oh dammit, I mixed this up with the other backout you did today.

But FWIW, I'm not entirely sure if mcomella and bnicholson prefer disabling this test so bug 962103 can re-land vs. re-enabling the test for now. I'll let them decide what they want to do.

(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #13) > This still failing frequently. I've disabled the test for now. > > https://hg.mozilla.org/integration/mozilla-inbound/rev/6a5325cc4c91 We backed this out on fx-team in bug 979038 comment 3 which was merged to central on bug 979038 comment 4. I'm confused about what the current state of the repo is, but yes, it should be disabled. needinfoing RyanVM so he can make sure there isn't a terrible inconsistency to fix now.

See bug 979038 comment 0 and bug 979038 comment 2 for suggestions how to fix this bug.

Basically, we're currently in a state where the test is disabled *and* your patch is backed out. Right now, I think we're at a point where one or the other can re-land, but I want that decision to be yours and Brian's rather than mine :)

Already ahead of you: bug 962103 landed earlier today :)

We are trying to move the Android 2.3 robocop jobs to aws slaves, where they generally run as reliably as on ix. testAboutHomeVisibility has been running reliably on Android 2.3 Opt and Android 2.3 Armv6 Opt, when run on ix slaves. Comment 27 shows an intermittent (low frequency?) failure in testAboutHomeVisibility when run on an aws slave.

(In reply to Geoff Brown [:gbrown] from comment #28) > testAboutHomeVisibility has been running reliably on Android 2.3 Opt and > Android 2.3 Armv6 Opt, when run on ix slaves. Comment 27 shows an > intermittent (low frequency?) failure in testAboutHomeVisibility when run on > an aws slave. I think this is actually bug 946656, which occurs on all Android versions - close if you agree. :)

Bug 946656 seems slightly more appropriate -- let's follow-up on the Android 2.3 failures of testAboutHomeVisibility there. ** Disregard comments 27 through 29. ** This bug should still not be closed since testAboutHomePageNavigation was disabled in this bug and remains disabled.

Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.