11:26:03 INFO - TEST-START | dom/presentation/tests/xpcshell/test_tcp_control_channel.js 11:26:03 WARNING - TEST-UNEXPECTED-FAIL | dom/presentation/tests/xpcshell/test_tcp_control_channel.js | xpcshell return code: 0 11:26:03 INFO - TEST-INFO took 305ms 11:26:03 INFO - >>>>>>> 11:26:03 INFO - (xpcshell/head.js) | test MAIN run_test pending (1) 11:26:03 INFO - (xpcshell/head.js) | test run_next_test 0 pending (2) 11:26:03 INFO - (xpcshell/head.js) | test MAIN run_test finished (2) 11:26:03 INFO - running event loop 11:26:03 INFO - dom/presentation/tests/xpcshell/test_tcp_control_channel.js | Starting loopOfferAnser 11:26:03 INFO - (xpcshell/head.js) | test loopOfferAnser pending (2) 11:26:03 INFO - NS_ERROR_FAILURE: Failure'Failure' when calling method: [nsITCPPresentationServer::init] 11:26:03 INFO - loopOfferAnser@/builds/slave/test/build/tests/xpcshell/tests/dom/presentation/tests/xpcshell/test_tcp_control_channel.js:64:3 11:26:03 INFO - _run_next_test@/builds/slave/test/build/tests/xpcshell/head.js:1391:11 11:26:03 INFO - do_execute_soon/<.run@/builds/slave/test/build/tests/xpcshell/head.js:653:9 11:26:03 INFO - _do_main@/builds/slave/test/build/tests/xpcshell/head.js:207:5 11:26:03 INFO - _execute_test@/builds/slave/test/build/tests/xpcshell/head.js:513:5 11:26:03 INFO - @-e:1:1 11:26:03 INFO - exiting test 11:26:03 INFO - (xpcshell/head.js) | test run_next_test 0 finished (2) 11:26:03 INFO - "CONSOLE_MESSAGE: (warn) [JavaScript Error: "uncaught exception: 2147500037"]" 11:26:03 INFO - <<<<<<<

Hello fabrice, This log is not informative enough, and I can not reproduce locally even if I test more than thousand times. If I can not reproduce in try server, I'd like to open the debug log in [nsITCPPresentationServer::init] to central. https://dxr.mozilla.org/mozilla-central/source/dom/presentation/provider/TCPPresentationServer.js#40 How do you think?

Junior, add a pref to turn on debug and set it in the testing profile, like we did for dom.mozApps.debug (see http://mxr.mozilla.org/mozilla-central/source/modules/libpref/init/all.js#4315 and http://mxr.mozilla.org/mozilla-central/source/testing/profiles/prefs_general.js#266)

last logs show "NS_ERROR_SOCKET_ADDRESS_IN_USE", maybe need some walk-around to try whether some ports are available or not.

The sudden resurgences in this (which are very probably some other failure which just happens to involve the same test and the same exit code) are due to the patch in bug 698882.

Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.

not happen in 1.5 years