retry unavailable ports rather than hard fail

[titusfortner]

I regularly have issues with a port being briefly unavailable. A short sleep fixes it.

This is a stack trace example: https://gist.github.com/titusfortner/6069aed4def5c1ea0db9
I've seen it happen with multiple wire calls, not just getCurrentWindowHandle

I've been running all of my tests with this monkey patched for the past month and have had no problems.

[andreastt]

LGTM. @titusfortner, did you sign the CLA?

This situation might occur when we exhaust the temporary port range on a machine with many TCP connections. It takes some time for the temporary sockets to be returned to the reusable pool, and in that short timespan there may be race conditions.

[titusfortner]

Yes, I have, thanks.
On Apr 3, 2015 5:19 AM, "Andreas Tolfsen" notifications@github.com wrote:

LGTM. @titusfortner https://github.com/titusfortner, did you sign the
CLA?

This situation might occur when we exhaust the temporary port range on a
machine with many TCP connections. It takes some time for the temporary
sockets to be returned to the reusable pool, and in that short timespan
there may be race conditions.

—
Reply to this email directly or view it on GitHub
#394 (comment).

[andreastt]

Thank you for the patch! I've integrated it as f0881e3.