Looks good to me. Don't know how many of those we've cleaned over the
years! ;)
Brad
On 1/18/2013 6:23 AM, Chris Hegarty wrote:
This test can be seen to fail intermittently on a very busy system. The
test tries to bind to a "hardcoded" (relative to another) port number. I
see no reason for
Looks good - I looked into the bug details for the test too, but could
not find any
reason why we would need server and client to bind to consecutive ports.
Thanks,
- Kurchi
On 1/18/13 6:23 AM, Chris Hegarty wrote:
This test can be seen to fail intermittently on a very busy system.
The test
This test can be seen to fail intermittently on a very busy system. The
test tries to bind to a "hardcoded" (relative to another) port number. I
see no reason for specify the port number in this testcase. The socket
needs to be bound to a specific address, but we should be able to
specify a por
