Closed Bug 947177 Opened 11 years ago Closed 11 years ago

Intermittent TEST-UNEXPECTED-FAIL | testAboutHomePageNavigation | Waiting for HomePager TOP_SITES page. -

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 947550

People

(Reporter: cbook, Assigned: mcomella)

References

(
URL
)

Details

Android 4.0 Panda mozilla-central opt test robocop-4 on 2013-12-05 15:39:59 PST for push 2831368a5e05

slave: panda-0862

https://tbpl.mozilla.org/php/getParsedLog.php?id=31527720&tree=Mozilla-Central

Mochi-Remote ERROR | Automation Error: Missing end of test marker (process crashed?)
7 INFO TEST-UNEXPECTED-FAIL | testAboutHomePageNavigation | Waiting for HomePager TOP_SITES page. -
Assignee: nobody → michael.l.comella
Blocks: 910859
Status: NEW → ASSIGNED
Note that the debug output is wrong and should be fixed by bug 947508.

This occurs after swiping from the initial page to the page on the right on an armv6 device. I have had this error happen locally where the issue is caused by the device not registering a full swipe to the next screen (typically because it is hanging/slow), thus scrolling back to the page it was initially on.

Some ideas:
  * Automatic retry if HomePager.getCurrentItem() does not change between swipes (con: We really shouldn't *have* to do this)
  * Wait a bit after each swipe to give the fragment more time to load and settle? The time between swipes seems very short and inhuman (con: longer tests)
bug 947527 landed and so the assertion failure output should be fixed. This is now the same as bug 947550.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.