Closed Bug 649564 Opened 10 years ago Closed 9 years ago

Intermittent failure in test_socks.js | test failed (with xpcshell return code: 0) | Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIProcess.kill]


(Core :: Networking, defect)

Not set



Tracking Status
firefox-esr10 --- fixed


(Reporter: philor, Assigned: michal)



(Keywords: intermittent-failure, Whiteboard: [qa-])


(1 file)

At least the second time, but last time I wasn't in the mood to file.
Rev3 MacOSX Leopard 10.5.8 mozilla-central opt test xpcshell on 2011/04/12 20:09:15
s: talos-r3-leopard-026

TEST-INFO | /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js | running test ...
TEST-UNEXPECTED-FAIL | /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js | test failed (with xpcshell return code: 0), see following log:
TEST-PASS | /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js | [null : 402] ==
server: all tests completed
server: client closed!
TEST-PASS | /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js | [null : 112] 8 == 8
server: test finished 8003
TEST-PASS | /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js | [null : 397] true == true
TEST-PASS | /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js | [null : 398] socks == socks
TEST-PASS | /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js | [null : 399] 8003 == 8003
TEST-PASS | /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js | [null : 402] ==
TEST-UNEXPECTED-FAIL | /Users/cltbld/talos-slave/test/build/xpcshell/head.js | exception thrown from do_timeout callback: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIProcess.kill]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: /Users/cltbld/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_socks.js :: <TOP_LEVEL> :: line 446"  data: no] - See following stack:
JS frame :: /Users/cltbld/talos-slave/test/build/xpcshell/head.js :: do_throw :: line 444
JS frame :: /Users/cltbld/talos-slave/test/build/xpcshell/head.js :: <TOP_LEVEL> :: line 158
TEST-INFO | (xpcshell/head.js) | exiting test
Assignee: nobody → michal.novotny
That thing where it failed 11 times in the first half of January, and then failed 30 times yesterday and today? Yeah, somebody should be worrying about that.
I don't see anything incriminating landing on inbound in the range of the 14th to the 17. It's conceivable that the test is simply wrong, and we started tickling it for unknown reasons - as far as I can tell, it's illegal to call kill() after the process has completed, but we have a timer in the test that calls it regardless, since we never reset this.client_subprocess to null (
I guess I could try retriggering this a bunch of times on try, or we could throw it at inbound and see if it makes a difference.
Try run for 989429c02b1e is complete.
Detailed breakdown of the results available here:
Results (out of 8 total builds):
    success: 8
Builds (or logs if builds failed) available at:
Are these new instances before or after your checkin?
Well, that didn't work. It failed on my push :(
That 'un is after, though :(