Opened 15 years ago

Closed 15 years ago

#3787 closed defect (fixed)

ContentPane unit test failing

Reported by: bill Owned by: mumme
Priority: high Milestone: 0.9
Component: Dijit Version: 0.9
Keywords: Cc:
Blocked By: Blocking:

Change History (3)

comment:1 Changed 15 years ago by mumme

(In [9749]) Extending timeouts on the async tests to see if it cures the failure in doh.runner We wait for 1.5 sec max on a response from the server. refs #3787

comment:2 Changed 15 years ago by mumme

Status: newassigned

This test actually works for me now (with extended timeouts) if I uncheck dijit.tests._Templated and click play button

Related info in #3856

I'm gone defer this bug until #3856 is fixed.

comment:3 Changed 15 years ago by mumme

Resolution: fixed
Status: assignedclosed

Seems Bill fixed this one when he fixed #3856

Works for me in IE6-7, Safari Win 3 beta, FF 2.0.6

It fails and still gives spurious errors in Opera and Konqueror seems that a doh continues to next test file when a test throws, if that tests has a setTimeout it will cause spurious event loops inside the browser. Though I haven't researched enough to be certain, in any case this seems to punish ContentPane? test as that takes the longest time to run through (30s) it runs about half the test, but is halted by the previous thrown file setTimeout's meaning 2 or in worst case multiple test "cursors" (couldn't find a better word) and that is bound to fail.

But it has nothing to to do with the ContentPane? test in it self (runs fine in both Konqueror and Opera if the previous tests that fails is unchecked).

So I'm closing this ticket. Not sure when I can find the time to investigate and prove or dismiss my above theory, don't want open a new ticket against doh.runner before I know more.

Note: See TracTickets for help on using tickets.