Intermittent test_bug393968.html | Test timed out. (followed by three more timeouts before giving up)

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
7 years ago
a month ago

People

(Reporter: emorley, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
Posted image Screenshot
Rev3 WINNT 5.1 mozilla-inbound opt test mochitests-1/5 on 2012-05-10 14:59:34 PDT for push 11816ca37b52

slave: talos-r3-xp-056

https://tbpl.mozilla.org/php/getParsedLog.php?id=11657323&tree=Mozilla-Inbound

{
12730 INFO TEST-START | /tests/content/base/test/test_bug393968.html
12731 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_bug393968.html | Test timed out.
args: ['c:\\talos-slave\\test\\build\\bin\\screenshot.exe', 'c:\\docume~1\\cltbld\\locals~1\\temp\\mozilla-test-fail_0ler-s']
SCREENSHOT: <attached>
12732 INFO TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_bug393968.html | finished in a non-clean fashion (in /tests/content/base/test/test_bug392511.html)
12733 INFO TEST-END | /tests/content/base/test/test_bug393968.html | finished in 320797ms
12734 INFO TEST-START | /tests/content/base/test/test_bug395915.html
12735 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_bug395915.html | Test timed out.
Not taking screenshot here: see the one that was previously logged
12736 INFO TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_bug395915.html | finished in a non-clean fashion (in /tests/content/base/test/test_bug392511.html)
12737 INFO TEST-END | /tests/content/base/test/test_bug395915.html | finished in 330013ms
12738 INFO TEST-START | /tests/content/base/test/test_bug397234.html
12739 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_bug397234.html | Test timed out.
Not taking screenshot here: see the one that was previously logged
12740 INFO TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_bug397234.html | finished in a non-clean fashion (in /tests/content/base/test/test_bug392511.html)
12741 INFO TEST-END | /tests/content/base/test/test_bug397234.html | finished in 329995ms
12742 INFO TEST-START | /tests/content/base/test/test_bug398243.html
12743 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_bug398243.html | Test timed out.
Not taking screenshot here: see the one that was previously logged
12744 ERROR TEST-UNEXPECTED-FAIL | (SimpleTest/TestRunner.js) | 4 test timeouts, giving up.
12745 ERROR TEST-UNEXPECTED-FAIL | (SimpleTest/TestRunner.js) | Skipping 772 remaining tests.
12746 INFO TEST-UNEXPECTED-FAIL | (SimpleTest/TestRunner.js) | finished in a non-clean fashion (in /tests/content/base/test/test_bug392511.html)
12747 INFO TEST-END | (SimpleTest/TestRunner.js) | finished in 330012ms
12748 INFO TEST-START | Shutdown
12749 INFO Passed: 12414
12750 INFO Failed: 22
12751 INFO Todo:   88
}
Is this repeatable ? 
Does anyone have any hypothesis ? 

I was thinking something in the harness could have hung, as each of the tests that timed out are differing quite significantly.
content/base/test/test_bug393968.html

the test that failed is the one listed in the bug, I can imagine adding more logging to this test file. There are probably just a few options of things that intermittently failed

1) XMLHttpRequest (some type of connection leakage, which would cause a new request to hang)
2) SpecialPowers.wrap
3) Test Harness

Maybe if we add more logging we can rule out some of these ?
It may be that a previous test which uses XMLHttpRequest is causing a problem, 
as I think there is a limit to the number of requests to a specific host, and if these requests were getting backed up, then maybe it could have an effect of this nature where the browser was unresponsive?


test_bug383430.html XMLHttpRequest -- mozBackgroundRequest
test_bug392511.html --none
test_bug393968.html XMLHttpRequest  -- unresponsive
test_bug395915.html --none          -- unresponsive
test_bug397234.html XMLHttpRequest  -- unresponsive

var req = new XMLHttpRequest();
req.mozBackgroundRequest = true;
req.open("GET", window.location.href);
req.send(null);

Possibly the tests could do a better job of cleaning up after itself by aborting things that fail, and then setting the req = null. But imagine we should wait for the patch to go in, and see if it happens again as we don't have enough data to act right now.
David - there is no reviewer set for this patch - still relevant for debugging?
Whiteboard: [orange]
(Reporter)

Comment 6

6 years ago
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of:
{random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open}

There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
Component: DOM: Mozilla Extensions → DOM
Product: Core → Core
Attachment #625751 - Flags: review?
Component: DOM → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.