Closed Bug 836815 Opened 12 years ago Closed 11 years ago

Intermittent testFlingCorrectness | Pixel at 0, 0 - Color rgba(0,101,33,255) not close enough to expected rgb(0,200,64)

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=19307974&tree=Mozilla-Inbound Android Tegra 250 mozilla-inbound opt test robocop on 2013-01-30 19:25:53 PST for push 3bccc06c75b2 slave: tegra-087 0 INFO SimpleTest START 1 INFO TEST-START | testFlingCorrectness 2 INFO TEST-PASS | testFlingCorrectness | Awesomebar URL typed properly - http://mochi.test:8888/tests/robocop/robocop_boxes.html should equal http://mochi.test:8888/tests/robocop/robocop_boxes.html 3 INFO TEST-PASS | testFlingCorrectness | Pixel at 0, 0 - Color rgba(0,0,0,255) close enough to expected rgb(0,0,0) 4 INFO TEST-PASS | testFlingCorrectness | Pixel at 100, 0 - Color rgba(24,101,0,255) close enough to expected rgb(32,100,0) 5 INFO TEST-PASS | testFlingCorrectness | Pixel at 0, 100 - Color rgba(0,101,33,255) close enough to expected rgb(0,100,32) 6 INFO TEST-PASS | testFlingCorrectness | Pixel at 100, 100 - Color rgba(24,203,33,255) close enough to expected rgb(32,200,32) 7 INFO TEST-UNEXPECTED-FAIL | testFlingCorrectness | Pixel at 0, 0 - Color rgba(0,101,33,255) not close enough to expected rgb(0,200,64) Exception caught during test! junit.framework.AssertionFailedError: 7 INFO TEST-UNEXPECTED-FAIL | testFlingCorrectness | Pixel at 0, 0 - Color rgba(0,101,33,255) not close enough to expected rgb(0,200,64) at junit.framework.Assert.fail(Assert.java:47) at org.mozilla.fennec.FennecMochitestAssert._logMochitestResult(FennecMochitestAssert.java:107) at org.mozilla.fennec.FennecMochitestAssert.ok(FennecMochitestAssert.java:136) at org.mozilla.fennec.FennecMochitestAssert.ispixel(FennecMochitestAssert.java:166) at org.mozilla.fennec.tests.PixelTest.checkScrollWithBoxes(PixelTest.java:88) at org.mozilla.fennec.tests.testFlingCorrectness.testFlingCorrectness(testFlingCorrectness.java:36) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:521) at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:204) at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:194) at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:186) at org.mozilla.fennec.tests.BaseTest.runTest(BaseTest.java:131) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169) at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154) at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:520) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1447) 8 INFO TEST-UNEXPECTED-FAIL | testFlingCorrectness | Exception caught - junit.framework.AssertionFailedError: 7 INFO TEST-UNEXPECTED-FAIL | testFlingCorrectness | Pixel at 0, 0 - Color rgba(0,101,33,255) not close enough to expected rgb(0,200,64) 9 INFO TEST-END | testFlingCorrectness | finished in 37517ms 10 INFO TEST-START | Shutdown 11 INFO Passed: 5 12 INFO Failed: 2 13 INFO Todo: 0 14 INFO SimpleTest FINISHED
I expect this may be a race when setting the browser.chrome.dynamictoolbar pref, but I've not done any investigation.
Blocks: 854284
Closing inactive keywords:intermittent-failure bugs where the TBPLbot has previously commented and the test isn't marked as disabled; filter on orange-cleanup-201401.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.