From: JINMEI Tatuya <jinmei@isc.org>
Date: Mon, 2 Jan 2012 06:28:09 +0000 (+0000)
Subject: [master] use a different TCP port for tests than that used in some other
X-Git-Tag: trac2351_base~310^2~4
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f8a705c023c49b646420b047da00b08ec67b1667;p=thirdparty%2Fkea.git

[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 2fced6b4cf..63d75c2bac 100644
--- 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 {