Intermittent testNewTab | Number of tabs increased - got 1, expected 2

RESOLVED FIXED in Firefox 31

Status

()

RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: emorley, Assigned: gbrown)

Tracking

({intermittent-failure})

Trunk
Firefox 33
ARM
Android
intermittent-failure
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox31 fixed, firefox32 fixed, firefox33 fixed, firefox-esr24 unaffected, firefox-esr31 unaffected)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
+++ This bug was initially created as a clone of Bug #897076 +++

Android 2.2 Tegra mozilla-central opt test robocop-1 on 2013-09-24 21:24:18 PDT for push 68d279364a8b

slave: tegra-168

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

{
0 INFO SimpleTest START
1 INFO TEST-START | testNewTab
EventExpecter: no longer listening for Gecko:Ready
2 INFO TEST-PASS | testNewTab | Checking elements - all elements present
3 INFO TEST-PASS | testNewTab | Initial number of tabs correct - 1 should equal 1
4 INFO TEST-PASS | testNewTab | waiting for add tab view - add tab view available
5 INFO TEST-PASS | testNewTab | waiting for urlbar text to gain focus - urlbar text gained focus
6 INFO TEST-PASS | testNewTab | URL typed properly - http://mochi.test:8888/tests/robocop/robocop_blank_01.html should equal http://mochi.test:8888/tests/robocop/robocop_blank_01.html
EventExpecter: no longer listening for DOMContentLoaded
waitForTest timeout after 4500 ms
7 INFO TEST-UNEXPECTED-FAIL | testNewTab | Number of tabs increased - got 1, expected 2
Exception caught during test!
junit.framework.AssertionFailedError: 7 INFO TEST-UNEXPECTED-FAIL | testNewTab | Number of tabs increased - got 1, expected 2
	at junit.framework.Assert.fail(Assert.java:47)
	at org.mozilla.fennec.FennecMochitestAssert._logMochitestResult(FennecMochitestAssert.java:111)
	at org.mozilla.fennec.FennecMochitestAssert.ok(FennecMochitestAssert.java:140)
	at org.mozilla.fennec.FennecMochitestAssert.is(FennecMochitestAssert.java:146)
	at org.mozilla.fennec.tests.testNewTab.testNewTab(testNewTab.java:43)
	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:149)
	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 | testNewTab | Exception caught - junit.framework.AssertionFailedError: 7 INFO TEST-UNEXPECTED-FAIL | testNewTab | Number of tabs increased - got 1, expected 2
}
Created attachment 810637 [details]
Screenshot from 2013-09-26 12:33:35.png

In the attached screenshot, t1.jpg / t2.jpg / t3.jpg show what the screen looks like as it changes during a normal run.

The prod.jpg screenshot was in the log and shows what the screen actually looked like, instead of the expected t2.jpg ... 

the "1" in it's tabcounter is slightly out of center and I'm guessing the test caught the thing during it's animation change from "1" -> "2" and the objects value hasn't reached the right count yet.
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
(Assignee)

Comment 35

4 years ago
Changes in bug 995696 (2014-07-07) may have fixed this.
(Reporter)

Comment 36

4 years ago
Let's call this fixed for now :-)
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Depends on: 995696
Resolution: --- → FIXED
Assignee: nobody → gbrown
status-firefox31: --- → fixed
status-firefox32: --- → fixed
status-firefox33: --- → fixed
status-firefox-esr24: --- → unaffected
status-firefox-esr31: --- → unaffected
Target Milestone: --- → Firefox 33
You need to log in before you can comment on or make changes to this bug.