877882 - Intermittent test_bug720538 | PaintExpecter - blockUtilClear timeout (x3)

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect)

Description

[Phil Ringnalda (:philor)]

+++ This bug was initially created as a clone of Bug #877737 +++

+++ This bug was initially created as a clone of Bug #797615 +++

Bug 797615 didn't fix every instance of this failure. Since the <del>testBookmark</del><ins>test_bug720538</ins> failure appears to have a different cause, better to track that in a new bug.

https://tbpl.mozilla.org/php/getParsedLog.php?id=23610249&tree=Cypress
Android Armv6 Tegra 250 cypress opt test robocop-1 on 2013-05-30 14:12:58 PDT for push 1b236820d6ae
slave: tegra-097

4 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | PaintExpecter - blockUtilClear timeout
junit.framework.AssertionFailedError: 4 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | PaintExpecter - blockUtilClear timeout
5 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | Exception caught - junit.framework.AssertionFailedError: 4 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | PaintExpecter - blockUtilClear timeout
05-30 14:41:40.744 I/Robocop ( 6829): 4 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | PaintExpecter - blockUtilClear timeout
05-30 14:41:40.784 I/Robocop ( 6829): junit.framework.AssertionFailedError: 4 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | PaintExpecter - blockUtilClear timeout
05-30 14:41:40.784 I/Robocop ( 6829): 5 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | Exception caught - junit.framework.AssertionFailedError: 4 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | PaintExpecter - blockUtilClear timeout
05-30 14:41:42.014 I/TestRunner( 6829): junit.framework.AssertionFailedError: 5 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | Exception caught - junit.framework.AssertionFailedError: 4 INFO TEST-UNEXPECTED-FAIL | test_bug720538 | PaintExpecter - blockUtilClear timeout

Comment 1

[Kartikaya Gupta (email:[e-mail])]

WTF! I just re-enabled this test after spamming try with it, and it was perfectly green. 80 runs on Android 2.2 opt here: https://tbpl.mozilla.org/?tree=Try&rev=9ed690190559

Comment 2

[Kartikaya Gupta (email:[e-mail])]

At least the proximate cause of this one is obvious:

05-30 14:40:05.124 D/RobocopMotionEventHelper( 6829): Triggering down at (100.0,100.0)
05-30 14:40:07.914 W/GeckoGlobalHistory( 6829): Rebuilding visited link set...
05-30 14:40:07.914 I/GeckoToolbar( 6829): zerdatime 1592296 - Throbber stop
05-30 14:40:07.924 D/GeckoFavicons( 6829): Requesting cancelation of favicon load (4)
05-30 14:40:07.924 D/GeckoFavicons( 6829): Cancelling favicon load (4)
05-30 14:40:07.934 I/GeckoToolbar( 6829): zerdatime 1592316 - Throbber stop
05-30 14:40:07.984 D/RobocopMotionEventHelper( 6829): Triggering up at (100.0,100.0)
05-30 14:40:10.534 D/RobocopMotionEventHelper( 6829): Triggering down at (100.0,100.0)
05-30 14:40:10.614 D/RobocopMotionEventHelper( 6829): Triggering up at (100.0,100.0)

The 2+ second gap between the touch down and the touch up means the "double tap" would have been interpreted as a long tap + tap, and therefore cause the test to fail. The question is why it MotionEventHelper stalled out between those two events.

Comment 3

[Ed Morley [:emorley]]

(OrangeWFM bugs not modified in > 2 months)