Closed Bug 539283 Opened 15 years ago Closed 13 years ago

mochitest-browser-chrome: sporadic timeout in browser_sidebarpanels_click.js and browser_sort_in_library.js (this._getCurrentActiveWin() is null)

Categories

(Toolkit :: Places, defect)

Product:
Toolkit
Component:
Places
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: dholbert, Unassigned)

References

Details

(Keywords: intermittent-failure) 

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1263312578.1263318564.21326.gz
Linux mozilla-central debug test everythingelse on 2010/01/12 08:09:38
s: moz2-linux-slave26
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/components/places/tests/browser/browser_sidebarpanels_click.js | Timed out

The "guilty" push isn't places-related, so this looks sporadic... Assuming randomorange for now.
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1264710797.1264713458.29334.gz
WINNT 5.2 mozilla-central debug test mochitest-other on 2010/01/28 12:33:17
s: win32-slave18
OS: Linux → All
Hardware: x86 → All
Summary: mochitest-browser-chrome: sporadic timeout in browser_sidebarpanels_click.js on Linux Debug tinderbox → mochitest-browser-chrome: sporadic timeout in browser_sidebarpanels_click.js on Debug tinderbox
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1267052071.1267054940.26626.gz
WINNT 5.2 mozilla-central debug test mochitest-other on 2010/02/24 14:54:31
s: win32-slave26
looks like it timed out then came back to life... either the timeout was not real (needs larger timeout) or focus was acting fancy and test continued after getting it back
since test opens popups i think it's a more a focus issue, and after the timeout when we moved to another test it detected the focus back and continued. the test takes a small time, so i don't think enlarging timeout makes sense.
Whiteboard: [orange] → [orange][needs investigation]
Summary: mochitest-browser-chrome: sporadic timeout in browser_sidebarpanels_click.js on Debug tinderbox → mochitest-browser-chrome: sporadic timeout in browser_sidebarpanels_click.js (this._getCurrentActiveWin() is null)
oh cool, we are using the sidebar and the window is not the active one...
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1273250863.1273251574.4428.gz
Linux mozilla-central opt test mochitest-other on 2010/05/07 09:47:43
s: moz2-linux-slave09
Depends on: 562998
This happened in browser_sort_in_library.js as well:

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1290796569.1290797602.6952.gz
Rev3 Fedora 12x64 mozilla-central opt test mochitest-other on 2010/11/26 10:36:09
Summary: mochitest-browser-chrome: sporadic timeout in browser_sidebarpanels_click.js (this._getCurrentActiveWin() is null) → mochitest-browser-chrome: sporadic timeout in browser_sidebarpanels_click.js and browser_sort_in_library.js (this._getCurrentActiveWin() is null)
bug 562998 is fixed, so this bug about "this._getCurrentActiveWin() is null" is fixed as well.

Other timeouts in timeout in browser_sidebarpanels_click.js are tracked in bug 619689 (about to be solved as well).
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [orange][needs investigation] → [orange]
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.