BIND 10 #2888: msgq unittest failure on OpenBSD

[BIND 10 Development]

#2888: msgq unittest failure on OpenBSD
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  very high     |                    Milestone:  Next-
           Component:  msgq          |  Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by vorner):

 As is commented in the test source, the goal is on the border between unit
 tests and system tests. It does test specific behaviour, but of the whole
 msgq.
 There's a lot of recv/send handling that is/(or at least was some time
 ago)
 broken and it is needed to check it.

 It seemed easier to write it as unit test than lettuce test. In lettuce,
 it
 would be easier to start the msgq, but then, keeping a connection open and
 sending and receiving data across it would be hell.

 As for the error, maybe it would be better to have the while to check it
 can
 connect instead of if the path exists. There may be a short time between
 the
 socket is created and msgq starts listening on it.

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