Closed
Bug 529860
Opened 15 years ago
Closed 14 years ago
Provide a method to enlarge timeout for some browser chrome tests
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9.3a1
People
(Reporter: mak, Assigned: mak)
References
Details
(Keywords: dev-doc-complete, Whiteboard: [automatic test commented out since would take too much time on tinderboxes])
Attachments
(1 file, 2 obsolete files)
2.65 KB,
patch
|
Details | Diff | Splinter Review |
bug 527614 brought this to SimpleTest, we have some b-c test that takes longer times (for example the tests in bug 507172 or in bug 525610) than others, and those tests are timing our randomly. The timeout should be large enough for any test, but looks like on VMs it has some strange behavior (like timing out in seconds rather than minutes)
Assignee | ||
Updated•15 years ago
|
Assignee | ||
Updated•15 years ago
|
Summary: evaluate if we want enlarged timeouts on b-c tests → Provide a method to enlarge timeout for some b-c tests
Assignee | ||
Comment 1•15 years ago
|
||
builds on top of patches in bug 528469 and bug 485269
Assignee | ||
Comment 2•15 years ago
|
||
(In reply to comment #0) > The timeout should be large enough for any test, but looks like on VMs it has > some strange behavior (like timing out in seconds rather than minutes) this is actually incorrect, the timeout in b-c is 30 seconds, while looks like mochitests have larger timeouts. the patch allows to extend the 30 seconds base value by an integer factor.
Assignee | ||
Updated•15 years ago
|
Summary: Provide a method to enlarge timeout for some b-c tests → Provide a method to enlarge timeout for some browser chrome tests
Assignee | ||
Comment 3•15 years ago
|
||
Attachment #416078 -
Attachment is obsolete: true
Attachment #416078 -
Flags: review?(gavin.sharp)
Assignee | ||
Updated•15 years ago
|
Flags: in-testsuite?
Assignee | ||
Comment 4•15 years ago
|
||
Comment on attachment 421860 [details] [diff] [review] patch v1.1 i'll push all three patches to tryserver
Attachment #421860 -
Flags: review?(gavin.sharp)
Assignee | ||
Updated•15 years ago
|
Whiteboard: to be applied on top of patch in bug 528469 and bug 485269
Comment 5•14 years ago
|
||
Comment on attachment 421860 [details] [diff] [review] patch v1.1 >diff --git a/testing/mochitest/browser-test.js b/testing/mochitest/browser-test.js > this.currentTest.scope.__waitTimer = setTimeout(function() { >+ if (--self.currentTest.scope.__timeoutFactor > 0) { >+ // Wait a bit longer. Maybe add a self.currentTest.scope.info("Waiting longer; __timeoutFactor: " + self.currentTest.scope.__timeoutFactor); ?
Attachment #421860 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Updated•14 years ago
|
Keywords: dev-doc-needed
Assignee | ||
Comment 6•14 years ago
|
||
addressed comment
Attachment #421860 -
Attachment is obsolete: true
Assignee | ||
Comment 7•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/baaa8aea09ab
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Flags: in-testsuite? → in-testsuite+
Resolution: --- → FIXED
Whiteboard: to be applied on top of patch in bug 528469 and bug 485269 → [automatic test commented out since would take too much time on tinderboxes]
Target Milestone: --- → mozilla1.9.3a1
Assignee | ||
Comment 8•14 years ago
|
||
updated docs in https://developer.mozilla.org/en/Browser_chrome_tests
Keywords: dev-doc-needed → dev-doc-complete
Updated•6 years ago
|
Component: BrowserTest → Mochitest
You need to log in
before you can comment on or make changes to this bug.
Description
•