If I uninstall/reinstall my build between each test, bug 947550 is 100% reproducible locally. This is even without bug 962103 applied (which was assumed to be the cause of bug 947550). Subsequent runs pass, so this only shows up on first run. Since this test is failing in a number of unexpected circumstances, we should disable it until we can get a better hold on the failures.

(In reply to Brian Nicholson (:bnicholson) from comment #0) > If I uninstall/reinstall my build between each test, bug 947550 is 100% > reproducible locally. This is even without bug 962103 applied (which was > assumed to be the cause of bug 947550). Subsequent runs pass, so this only > shows up on first run. This test has a chance of failing if the device is otherwise busy (i.e. the swipe gesture is not read very well by the system). Since this failure occurs on the first run frequently, that probably means creating the profile, or other initialization, is causing these issues. We should probably check to see what might have affected the startup code path when this regressed, because it may have affected startup performance.

We'll re-enable and hopefully fix this in bug 977952.

(In reply to Michael Comella (:mcomella) from comment #5) > We'll re-enable and hopefully fix this in bug 977952. Or maybe one of the original bugs x_x: * Waiting for BOOKMARKS: bug 947550 * Toolbar is Yahoo/Wiki/etc.: bug 952046

(In reply to Michael Comella (:mcomella) from comment #2) > This test has a chance of failing if the device is otherwise busy (i.e. the > swipe gesture is not read very well by the system). Since this failure > occurs on the first run frequently, that probably means creating the > profile, or other initialization, is causing these issues. This sounds vaguely like Bug 978497. Thoughts?

(In reply to Richard Newman [:rnewman] from comment #7) > This sounds vaguely like Bug 978497. Thoughts? Could be related, on the basis of Gecko taking priority over the UI (which I imagine should generally not happen). However, since this test is entirely in the HomePager (i.e. about:home) and the failure occurs only(?) on the first run, it seems to be an issue with creating the profile.