Closed Bug 968783 Opened 12 years ago Closed 11 years ago

Intermittent B2G emulator ajax/jquery/test_jQuery.html | Test timed out.

Categories

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

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla34
Tracking Status
firefox32 --- fixed
firefox33 --- fixed
firefox34 --- fixed
firefox-esr24 --- unaffected
firefox-esr31 --- unaffected
b2g-v1.4 --- unaffected
b2g-v2.0 --- fixed
b2g-v2.1 --- fixed

People

(Reporter: cbook, Assigned: u459114)

References

()

Details

(Keywords: intermittent-failure)

Attachments

(1 file, 1 obsolete file)

b2g_emulator_vm mozilla-inbound opt test mochitest-7 on 2014-02-06 02:55:05 PST for push 84b6f0aba30d slave: tst-linux64-spot-317 https://tbpl.mozilla.org/php/getParsedLog.php?id=34203455&tree=Mozilla-Inbound 1351 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | Test timed out. 1356 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | [SimpleTest.finish()] this test already called finish! 1357 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | called finish() multiple times [Child 742] ###!!! ABORT: constructor for actor failed: file PLayerTransactionChild.cpp, line 133
Lots of these on b2g28 as well. Looks like this is legitimately running slowly. From the log: 03:26:04 INFO - 1339 INFO TEST-START | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html 03:32:21 INFO - 1351 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | Test timed out. Jonathan, maybe another symptom of the general slowdowns we're seeing?
Summary: Intermittent TEST-UNEXPECTED-FAIL | ajax/jquery/test_jQuery.html | Test timed out. → Intermittent B2G emulator ajax/jquery/test_jQuery.html | Test timed out.
You didn't disable dom-level* on b2g28, did you? From the timing when this started to appear, I thought it was the result of jQuery moving to a new chunk where it wasn't happy.
Not yet.
Rob, as the reviewer of the cset that imported this test into the tree - could you take a look or find someone who would be able to? This test is failing extremely frequently on B2G and soon going to be disabled under the test disabling policy otherwise. Thanks :-)
Flags: needinfo?(rcampbell)
jst, as module owner, could you find someone to look at this top orange on B2G? (escalating per https://wiki.mozilla.org/Sheriffing/Test_Disabling_Policy). (150 failures on trunk in the last week alone). Thanks :-)
Whiteboard: [disableme 2014-08-25]
(In reply to Ed Morley [:edmorley] from comment #490) > jst, as module owner, could you find someone to look at this top orange on > B2G? (escalating per > https://wiki.mozilla.org/Sheriffing/Test_Disabling_Policy). (150 failures on > trunk in the last week alone). Thanks :-)
Flags: needinfo?(jst)
I am not sure whether this information is useful here, but one of my change make this bug 100% repro able. Share the link here https://tbpl.mozilla.org/?tree=Try&rev=f6ac411d8051 What I did in those patches is try to prevent duplicate setfullzoom while contentviewer switch.
:cjku, given that you can reproduce this 100% can you look into gathering more information here? I.e. stacks for any failures, that don't show up in the logs, what's the behavior here, is this test running along, just takes more than 5 minutes to run and then times out? Or does it actually appear to get stuck somewhere? Thanks!
Flags: needinfo?(jst) → needinfo?(cku)
I meant to clarify that what I'm asking for is how this test behaves locally, i.e. do you see the failures when running on a device locally, and what is the behavior then. Thanks.
Attached patch Give test_jQuery more time (obsolete) — — Splinter Review
I was wrong, after re-trigger more jobs on TPBL, it turns out only 60% fail rate. I ran this test case on my pc(Intel Core i7-3770 @ 3.4GHz, 16G RAM). Around 270 seconds to finish test_jQuery. My PC stays in a very happy circumstance, no overload jobs assigned to it. Even though, it still took 270 seconds to finish this test case. By looking into full logs on TBPL, timeout appeared on different sub test cases and no native crash. I think this test case is literally a "timeout" problem. To verify my assumption, let's jut extend timeout duration and see the result on try: https://tbpl.mozilla.org/?tree=Try&rev=fa84bcb9a29d
Flags: needinfo?(cku)
Extend timeout duration to 600 seconds. Result looks quite promising, many of them should be failed before timeout extending: test_jQuery.html | took 260329ms test_jQuery.html | took 283635ms test_jQuery.html | took 278023ms test_jQuery.html | took 276327ms test_jQuery.html | took 256865ms test_jQuery.html | took 257723ms test_jQuery.html | took 239156ms test_jQuery.html | took 276682ms test_jQuery.html | took 277090ms test_jQuery.html | took 285844ms test_jQuery.html | took 261215ms test_jQuery.html | took 286732ms test_jQuery.html | took 274857ms test_jQuery.html | took 268072ms test_jQuery.html | took 274878ms test_jQuery.html | took 263869ms test_jQuery.html | took 315747ms << boom test_jQuery.html | took 322559ms << boom test_jQuery.html | took 268072ms test_jQuery.html | took 312006ms << boom test_jQuery.html | took 274878ms test_jQuery.html | took 263869ms test_jQuery.html | took 339051ms << boom test_jQuery.html | took 339051ms << boom test_jQuery.html | took 315747ms << boom
test_jQuery.html | took 270129ms test_jQuery.html | took 269392ms test_jQuery.html | took 327183ms << boom test_jQuery.html | took 269392ms test_jQuery.html | took 287548ms test_jQuery.html | took 315604ms << boom test_jQuery.html | took 304686ms test_jQuery.html | took 284205ms test_jQuery.html | took 273553ms test_jQuery.html | took 337870ms << boom test_jQuery.html | took 324265ms << boom
Attached patch Give test_jQuery more time — — Splinter Review
Attachment #8477208 - Attachment is obsolete: true
Comment on attachment 8477267 [details] [diff] [review] Give test_jQuery more time Review of attachment 8477267 [details] [diff] [review]: ----------------------------------------------------------------- LGTM, thanks!
Attachment #8477267 - Flags: review+
https://hg.mozilla.org/integration/b2g-inbound/rev/805ca0f44c0c CJ, can you please include your full name in your hg commit information in the future? Thanks!
Assignee: nobody → cku
Flags: in-testsuite+
Whiteboard: [disableme 2014-08-25]
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Flags: needinfo?(rcampbell)
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: