518317 - chrome test_bug413909.html and others intermitently fail, "failed to bind socket" message from ssltunnel

Status: RESOLVED WORKSFORME

(Core :: Security: PSM, defect)

Description

[Honza Bambas (:mayhemer)]

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.6/1253649196.1253660076.30079.gz, search for 'failed to bind socket'

As there is also test_bug480619.html failing with NS_ERROR_CONNECTION_REFUSED error, I can confirm this bug comes from failure of ssltunnel to bind its server socket.

Just above this error there is: "buildbot.slave.commands.TimeoutError: command timed out: 300 seconds without output, killing pid 18701"

Seems to me that ssltunnel has not been killed in this case keping the socket, we should kill all processes spawned by automation.py probably.

Comment 1

[Ed Morley [:emorley]]

Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500