Closed Bug 649127 Opened 10 years ago Closed 10 years ago

Intermittent timeout in browser/base/content/test/tabview/browser_tabview_rtl.js | application timed out after 330 seconds with no output

Categories

(Firefox Graveyard :: Panorama, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 6

People

(Reporter: ehsan.akhgari, Assigned: ttaubert)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file, 1 obsolete file)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1302552420.1302554125.28131.gz
Rev3 WINNT 5.1 mozilla-central opt test mochitest-other on 2011/04/11 13:07:00

TEST-START | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_rtl.js
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_rtl.js | Tab View starts hidden
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_rtl.js | application timed out after 330 seconds with no output
INFO | automation.py | Application ran for: 0:08:59.469000
INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmpjhejuppidlog
==> process 252 launched child process 1392
INFO | automation.py | Checking for orphan process with PID: 1392
Assignee: nobody → tim.taubert
Status: NEW → ASSIGNED
Version: unspecified → Trunk
Attached patch patch v1 (obsolete) — Splinter Review
Attachment #525457 - Flags: feedback?(raymond)
Comment on attachment 525457 [details] [diff] [review]
patch v1

Do you know what's the cause of the problem? Is that because tabViewCommand.doCommand() is not reliable?
The doCommand() does fail sometimes. Maybe when the window lost its focus? AFAIK there was some other test that was failing intermittently because of this, right? I just figured that this test doesn't really need to trigger the command directly :)
We can use waitForFocus to make sure that the test window is focused, if that's necessary.
(In reply to comment #4)
> We can use waitForFocus to make sure that the test window is focused, if that's
> necessary.

Yeah I know, from your docs about intermittently failing tests :) But IMHO we don't really need to test here if the command is working because that test is about LTR/RTL.
Comment on attachment 525457 [details] [diff] [review]
patch v1

Looks good.
Attachment #525457 - Flags: feedback?(raymond) → feedback+
Attachment #525457 - Flags: review?(ian)
Comment on attachment 525457 [details] [diff] [review]
patch v1

r=me as the author of the test, and someone who wants our orange bugs to get fixed ASAP!
Attachment #525457 - Flags: review?(ian) → review+
Keywords: checkin-needed
http://hg.mozilla.org/projects/cedar/rev/a51ecdeca4a8
Keywords: checkin-needed
Whiteboard: [orange] → [orange][fixed-in-cedar]
Target Milestone: --- → Firefox 6
http://hg.mozilla.org/mozilla-central/rev/a51ecdeca4a8
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [orange][fixed-in-cedar] → [orange]
Whiteboard: [orange]
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.