Closed Bug 885878 Opened 12 years ago Closed 12 years ago

DOM imptests can time out

Categories

(Core :: DOM: Core & HTML, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla28
Tracking Status
firefox28 --- fixed

People

(Reporter: ehsan.akhgari, Assigned: Ms2ger)

Details

(Whiteboard: [qa-])

Attachments

(1 file)

See <https://tbpl.mozilla.org/php/getParsedLog.php?id=24434726&tree=Mozilla-Inbound&full=1> for example. We already disabled testharness.js timeouts: <http://mxr.mozilla.org/mozilla-central/source/dom/imptests/testharnessreport.js#294>... or, did we? Turns out that because of this line <http://hg.mozilla.org/mozilla-central/annotate/61c3c8b85563/dom/imptests/testharness.js#l1209>, the testharness.js framework was setting up its timeout mechanism way before setup() was ever called. That's insane. I'm landing an unreviewed patch to fix that. Ms2ger, I'd appreciate if you post-review it. Thanks!
Flags: needinfo?(Ms2ger)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
Please submit this patch upstream.
Status: RESOLVED → REOPENED
Flags: needinfo?(Ms2ger) → needinfo?(ehsan)
Resolution: FIXED → ---
Sure. Can you please tell me where I need to submit it exactly?
Flags: needinfo?(ehsan)
Can you please tell me what the review of that upstream submission said?
Flags: needinfo?(Ms2ger)
> This looks wrong to me. > > If there is no call to setup() in the test, the timeout will never be set, which is wrong. > > You probably want to make setting explicit_timeout in the testharnessreport.js > file have the effect of clearing any existing timeout on the tests object, but > not setting a new one. Ehsan, can you address that?
Flags: needinfo?(Ms2ger) → needinfo?(ehsan)
OK, my patch was accepted upstream, what should we do about this bug now?
Flags: needinfo?(Ms2ger)
Attached patch Patch v1Splinter Review
Assignee: ehsan → Ms2ger
Status: REOPENED → ASSIGNED
Attachment #8336750 - Flags: review?
Flags: needinfo?(Ms2ger)
This is upstream code, it shouldn't need review.
Attachment #8336750 - Flags: review? → review?(james)
Attachment #8336750 - Flags: review?(james) → review+
Status: ASSIGNED → RESOLVED
Closed: 12 years ago12 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: mozilla24 → mozilla28
Whiteboard: [qa-]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: