Closed Bug 676696 Opened 13 years ago Closed 13 years ago

Intermittent browser_webconsole_bug_618311_private_browsing.js | Test timed out followed by | correct number of popups shown - Got 0, expected 2 and an unexpected tab

Categories

(DevTools :: General, defect)

Product:
DevTools
Component:
General
Platform:
x86_64
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Assigned: getify)

References

Details

(Keywords: intermittent-failure) 

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1312489895.1312492987.23238.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitest-other on 2011/08/04 13:31:35
s: talos-r3-snow-020

TEST-INFO | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser/browser_webconsole_bug_618311_private_browsing.js | Console message: trace: tabview assert: item must be given
UI_setActive(null)@chrome://browser/content/tabview.js:8129
collapse()@chrome://browser/content/tabview.js:8961
finalize([object MouseEvent])@chrome://browser/content/tabview.js:8978
([object MouseEvent])@chrome://browser/content/tabview.js:770
([object MouseEvent])@chrome://browser/content/tabview.js:740
synthesizeMouse([object XULElement],2,2,[object Object])@chrome://mochikit/content/tests/SimpleTest/EventUtils.js:228
tabLoaded([object Event])@chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser/browser_webconsole_bug_618311_private_browsing.js:147

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser/browser_webconsole_bug_618311_private_browsing.js | Test timed out
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser/browser_webconsole_bug_618311_private_browsing.js | correct number of popups shown - Got 0, expected 2
INFO TEST-END | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser/browser_webconsole_bug_618311_private_browsing.js | finished in 30099ms
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/webconsole/test/browser/browser_webconsole_bug_618311_private_browsing.js | Found a tab after previous test timed out: about:blank
And I seem to have skipped my standard "And 'timed out followed by' is a clear sign that the test needs to meet and develop a close relationship with the lovely registerCleanupFunction(), so it can actually stop running when it times out."
Mihai, can you please take a look into this?
I will look into this.
Assignee: nobody → getify
I would suspect:

changeset:   73767:6f1affa4bb5e
user:        Tim Taubert <tim.taubert@gmx.de>
date:        Thu Aug 04 03:49:43 2011 +0200
summary:     Bug 666475 - Intermittent browser_tabview_privatebrowsing.js | Test timed out; r=ehsan

changeset:   73766:1a9f0823fdba
user:        Tim Taubert <tim.taubert@gmx.de>
date:        Thu Aug 04 03:49:38 2011 +0200
summary:     Bug 651643 - Private browsing service executes transition even when no mode switch required; r=ehsan,zpao

(looked through hg log)

I would also suspect:

changeset:   73845:183aba2199bf
user:        Mihai Sucan <mihai.sucan@gmail.com>
date:        Wed Aug 03 21:04:30 2011 +0300
summary:     Bug 672470 - Fix memory leaks in Web Console code; r=rcampbell,gavin.sharp

But this landed on the 3rd of August, and the intermittent failures started on the 5th. So, I would first suspect Tim's changes which landed much closer to when the failures started, and they do touch private browsing stuff.
Looked into bug 651643 and I would single out that patch as a potential cause for the intermittent failures. Maybe I am completely wrong, hehe.

Tim: do you have ideas why would our test fail because of the PB changes? Thank you!
Knock on wood, but this failure stopped being starred fairly abruptly on the 22nd.  Might be worth looking for related changes in that timeframe.
Hasn't happened in over a week.  I'm gonna call this one fixed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [orange]
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.