Browse Source
[master] use a different TCP port for tests than that used in some other
[master] use a different TCP port for tests than that used in some other
tests. using the same port could make it fail on some build bots due to
failure in bind() with a conflicting socket in the time wait state.
this is a fragile workaround, but I expect we'll revist these test scenarios
with the introduction of socket creator anyway, so I chose to work this around
with a simplest fix.
JINMEI Tatuya
1 changed files with 1 additions and 1 deletions
+ 1
- 1
src/bin/resolver/tests/resolver_config_unittest.cc
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||