[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.

diff --git a/src/bin/resolver/tests/resolver_config_unittest.cc b/src/bin/resolver/tests/resolver_config_unittest.cc
index 2fced6b4cfe9ef7e9d84556a7d6eccad81ccf7bf..63d75c2bac3288d155d51982a4dc2eb82754c3a1 100644 (file)
--- a/src/bin/resolver/tests/resolver_config_unittest.cc
+++ b/src/bin/resolver/tests/resolver_config_unittest.cc
@@ -63,7 +63,7 @@ using isc::UnitTestUtil;
 
 namespace {
 const char* const TEST_ADDRESS = "127.0.0.1";
-const char* const TEST_PORT = "53535";
+const char* const TEST_PORT = "53530";
 
 // An internal exception class
 class TestConfigError : public isc::Exception {