BIND 10 #3244: Hardcoded UDP port causes test failures

BIND 10 Development do-not-reply at isc.org
Wed Dec 4 10:18:04 UTC 2013


#3244: Hardcoded UDP port causes test failures
-------------------------------+-----------------------------------------
            Reporter:  shane   |                        Owner:
                Type:  defect  |                       Status:  new
            Priority:  medium  |                    Milestone:  New Tasks
           Component:  dhcp    |                   Resolution:
            Keywords:          |                 CVSS Scoring:
           Sensitive:  0       |              Defect Severity:  Low
         Sub-Project:  DHCP    |  Feature Depending on Ticket:
Estimated Difficulty:  0       |          Add Hours to Ticket:  0
         Total Hours:  0       |                    Internal?:  0
-------------------------------+-----------------------------------------

Comment (by kean):

 The problem is that as I currently understand lettuce (which is admittedly
 incomplete) the tests are not easily parameterized. There are also a
 number of data files that have specific port values in them. #2904 does
 mitigate the problem somewhat by using ports that are less likely to be
 occupied. Very even boundary ports like 10000, 10001 etc are high risk for
 some other thing using the port. Of course simply using a higher port is
 no *guarantee* but it does reduce the liklihood significantly.

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


More information about the bind10-tickets mailing list