Closed Bug 599207 Opened 15 years ago Closed 14 years ago

"TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | test 2 took too long to finish!" and others

Categories

(Core :: Networking: WebSockets, defect)

Product:
Core
Component:
Networking: WebSockets
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: cjones, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1285284837.1285288185.1874.gz WINNT 5.2 mozilla-central debug test mochitests-1/5 on 2010/09/23 16:33:57 s: win32-slave07 29163 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | test 2 took too long to finish! 29170 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | the ws connection in test 6 should be closed cleanly 29171 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | test 6 took too long to finish! 29175 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | the ws connection in test 8 should be closed cleanly 29180 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | the ws connection in test 10 should be closed cleanly 29181 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | test 10 took too long to finish! 29185 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | the ws connection in test 11 should be closed cleanly 29187 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | test 12 took too long to finish! 29189 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | the ws connection in test 13 should be closed cleanly 29190 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | test 13 took too long to finish! 29192 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | the ws connection in test 14 should be closed cleanly 29196 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | Test timed out. 29199 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket_hello.html | the ws connection in test 16 should be closed cleanly 29200 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket_hello.html | Test timed out. 29204 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_ws_basic_tests.html | All the messages should have been processed! - got 4, expected 0 29205 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_ws_basic_tests.html | Didn't receive all the messages! - got 0, expected 1000 29206 ERROR TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_ws_basic_tests.html | Didn't receive all the messages! - got 0, expected 100 This happened on http://hg.mozilla.org/mozilla-central/rev/626d22af7eff, but there's really no chance it caused this. The machines were under very high load around this push, and there were several other timeouts.
Whiteboard: [orange]
OS: Linux → All
Hardware: x86_64 → All
Summary: Windows Md1 "TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | test 2 took too long to finish!" and others → "TEST-UNEXPECTED-FAIL | /tests/content/base/test/test_websocket.html | test 2 took too long to finish!" and others
Component: Networking → Networking: WebSockets
QA Contact: networking → networking.websockets
comment 10 is mis-starred; filed a new bug 677840
this orange has been squashed. many more bugs still remain but now you are closed.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.