BIND 10 #1772: "two bind10 instances" lettuce test fails

BIND 10 Development do-not-reply at isc.org
Wed Mar 28 12:25:59 UTC 2012


#1772: "two bind10 instances" lettuce test fails
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20120403
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  Boss   |           Sub-Project:  DNS
  of BIND                            |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  0.5
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  UnAssigned => jinmei
 * totalhours:  0 => 0.5


Comment:

 I'm fine with any range of ports or addresses, btw.  Also don't mind ::1,
 though I do wonder if we want to be able to run this on non-v6 machine (if
 not, then all is fine imo, in fact, it may be good to explicitely test v6
 as well). I was wondering, perhaps we can also default to different
 127.0.0.0/8 addresses (ie. 127.0.0.5 or whatever).

 I don't really feel like building in some unused-port-detection for this
 class of listening ports, but perhaps we can write a small tool that finds
 one (obviously, such a setup would be subject to race conditions if other
 applications steal it between the finding and the running of the tests),
 but even for that I wonder if it's worth the trouble.

 I do worry about that loop; but not sure how it can be prevented if it is
 talking to a totally different application.

 Anyway, I think this branch is fine to merge as an interim solution.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1772#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list