Closed Bug 689328 Opened 14 years ago Closed 13 years ago

Intermittent ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | event type while running data for without length, as xml for moz-json[0] (or document[0], etc.) - got load, expected progress, followed by other errors

Categories

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

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla18
Tracking Status
firefox17 --- fixed

People

(Reporter: mbrubeck, Assigned: khuey)

References

Details

(Keywords: intermittent-failure)

Attachments

(2 files)

https://tbpl.mozilla.org/php/getParsedLog.php?id=6556255&tree=Firefox Rev3 WINNT 6.1 x64 mozilla-central opt test mochitests-1/5 on 2011-09-26 12:55:47 PDT for push 48df3b328875 41229 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | length should be computable during loadend closing with length for moz-json - true should equal true 41230 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | should readystate to headers-received starting without length, as xml for moz-json - readystatechange should equal readystatechange 41231 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | should be in state HEADERS_RECEIVED starting without length, as xml for moz-json - 2 should equal 2 41232 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | should readystate to loading starting without length, as xml for moz-json - readystatechange should equal readystatechange 41233 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | should be in state LOADING starting without length, as xml for moz-json - 3 should equal 3 41234 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | event type while running data for without length, as xml for moz-json[0] - progress should equal progress 41235 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | response should be null while running data for without length, as xml for moz-json[0] - null should equal null 41236 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | event.loaded increased while running data for without length, as xml for moz-json[0] 41237 INFO TEST-PASS | /tests/content/base/test/test_xhr_progressevents.html | event.loaded didn't increase too much while running data for without length, as xml for moz-json[0] 41238 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | lengthComputable while running data for without length, as xml for moz-json[0] - got true, expected false 41239 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | event type while running data for without length, as xml for moz-json[1] - got load, expected progress 41240 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | [SimpleTest/SimpleTest.js, window.onerror] - An error occurred: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXMLHttpRequest.response]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://mochi.test:8888/tests/content/base/test/test_xhr_progressevents.html :: updateProgress :: line 35" data: no] at :0 41241 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | [SimpleTest/SimpleTest.js, window.onerror] - An error occurred: uncaught exception: [object StopIteration] at :0 41242 INFO TEST-END | /tests/content/base/test/test_xhr_progressevents.html | finished in 5260ms 41243 INFO TEST-START | /tests/content/canvas/test/crossorigin/test_canvas2d_crossorigin.html *** error running SJS at c:\talos-slave\test\build\mochitest\tests\content\base\test\progressserver.sjs: TypeError: getReq() is null on line 43 41244 INFO TEST-END | /tests/content/canvas/test/crossorigin/test_canvas2d_crossorigin.html | finished in 38ms 41245 INFO TEST-START | /tests/content/canvas/test/crossorigin/test_webgl_crossorigin_textures.html
Summary: Intermittent ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | lengthComputable while running data for without length, as xml for moz-json[0] - got true, expected false, followed by other errors → Intermittent ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | lengthComputable while running data for without length, as xml for moz-json[0] (or document[0], etc.) - got true, expected false, followed by other errors
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1331516628.1331519909.18473.gz WINNT 5.2 comm-central-trunk debug test mochitests-1/5 on 2012/03/11 18:43:4840313 ERROR { { TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | lengthComputable while running data for without length, as xml for document[0] - got true, expected false [...] }
https://tbpl.mozilla.org/php/getParsedLog.php?id=10777684&tree=Firefox Rev3 WINNT 6.1 mozilla-central debug test mochitests-1/5 on 2012-04-10 09:01:08 PDT for push 2374ebd5026f { 44846 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | lengthComputable while running data for without length, as xml for moz-chunked-arraybuffer[0] - got true, expected false 44848 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | event type while running data for without length, as xml for moz-chunked-arraybuffer[1] - got load, expected progress 44849 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | response should be an ArrayBuffer while running data for without length, as xml for moz-chunked-arraybuffer[1] 44850 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | an unexpected uncaught JS exception reported through window.onerror - invalid arguments at http://mochi.test:8888/tests/content/base/test/test_xhr_progressevents.html:115 44851 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | an unexpected uncaught JS exception reported through window.onerror - uncaught exception: [object StopIteration] at :0 44854 INFO TEST-UNEXPECTED-FAIL | /tests/content/base/test/websocket_hybi/test_receive-arraybuffer.html | finished in a non-clean fashion (in /tests/content/base/test/test_xhr_progressevents.html) }
OS: Windows 7 → All
Hardware: x86_64 → All
600 failures in, does anyone have any ideas about this one? :-) (it's a regular top orange)
I caught this in the VM; I think this may be a regression from http://hg.mozilla.org/mozilla-central/rev/dee5413476bb. Need to play with it more on Monday.
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #627) > I caught this in the VM; I think this may be a regression from > http://hg.mozilla.org/mozilla-central/rev/dee5413476bb. > > Need to play with it more on Monday. Thank you :-D
Attached patch Patch — — Splinter Review
Assignee: nobody → khuey
Status: NEW → ASSIGNED
Attachment #649386 - Flags: review?(jonas)
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #630) > Patch <3 :-D
Comment on attachment 649386 [details] [diff] [review] Patch Review of attachment 649386 [details] [diff] [review]: ----------------------------------------------------------------- You rock for finding and fixing this!
Attachment #649386 - Flags: review?(jonas) → review+
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
(In reply to TinderboxPushlog Robot from comment #638) > philor > https://tbpl.mozilla.org/php/getParsedLog.php?id=14246783&tree=Firefox > Rev3 WINNT 6.1 mozilla-central debug test mochitests-1/5 on 2012-08-08 > 20:53:16 > slave: talos-r3-w7-046 > > 45047 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | event type while > running data for without length, as xml for [1] - got load, expected progress > 45051 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | event.loaded > increased while running data for without length, as xml for [1] > 45054 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | sanity check for > progress while running data for without length, as xml for [1] > 45056 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | lengthComputable > while running data for without length, as xml for [1] - got true, expected > false > 45057 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | event type while > running data for without length, as xml for [1] - got loadend, expected > progress > 45061 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | event.loaded > increased while running data for without length, as xml for [1] > 45064 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | sanity check for > progress while running data for without length, as xml for [1] > 45066 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | lengthComputable > while running data for without length, as xml for [1] - got true, expected > false > 45067 ERROR TEST-UNEXPECTED-FAIL | > /tests/content/base/test/test_xhr_progressevents.html | Test timed out. lengthComputable mismatch is no longer reported but the problem is not solved.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Intermittent ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | lengthComputable while running data for without length, as xml for moz-json[0] (or document[0], etc.) - got true, expected false, followed by other errors → Intermittent ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_xhr_progressevents.html | event type while running data for without length, as xml for moz-json[0] (or document[0], etc.) - got load, expected progress, followed by other errors
It seems like what's happening now is that the mochitest http server is losing track of the request. In particular: * We're getting a "load" event much too prematurely, I'm guessing because the server closes the http connection rather than keeping it open in order to send more data to it. * There is always an error coming from the SJS file right after the failed test: progressserver.sjs: TypeError: getReq(...) is null on line 43 What *should* be happening is that progressserver.sjs should be storing the request using setObjectState and then sending data on it later. However it appears that the request is somehow getting closed. Either this could be due to weirdness on the server side with the server losing the stored object state. Or it could be that a stray 'close' command is sent to progressserver.js which will cause it to close the connection. What's weird is that this always happens on the "without length, as xml" test. I wonder if it's somehow related to the fact that the previous test does have a length which means that we could be closing the channel without an explicit close command being sent to progressserver.js
Attached patch Potential fix — — Splinter Review
This might fix it. I haven't been able to reproduce the problem locally though so I can't know for certain. It passes locally and on try though.
Attachment #657231 - Flags: review?(khuey)
Comment on attachment 657231 [details] [diff] [review] Potential fix Review of attachment 657231 [details] [diff] [review]: ----------------------------------------------------------------- It's worth a shot.
Attachment #657231 - Flags: review?(khuey) → review+
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Oops, didn't mean to mark as fixed since it's not on m-c yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Target Milestone: mozilla17 → mozilla18
Whiteboard: [orange]
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: