BIND 10 #2790: Lettuce tests timing & missed messages

[BIND 10 Development]

#2790: Lettuce tests timing & missed messages
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  vorner                             |                Status:  new
                       Type:         |             Milestone:  New Tasks
  defect                             |              Keywords:
                   Priority:         |             Sensitive:  0
  medium                             |           Sub-Project:  Core
                  Component:         |  Estimated Difficulty:  0
  Unclassified                       |           Total Hours:  0
               CVSS Scoring:         |
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 The lettuce tests fail quite often, usually by waiting for some message to
 appear. However, the message seems to present in the log output file.
 Also, it didn't seem to have any garbage around, as suggested elsewhere.

 My wild guess of what might be happening:
  * A lot of messages are output at once.
  * Lettuce checks in intervals. There's more than one mouthful of messages
 at the next check.
  * Kernel provides only something like 4k of messages at the next read,
 splitting one of the messages at the end of the block.
  * Lettuce gets confused about the partial message.

 But looking at it again, this seems like an unlikely situation. Could it
 be that write of single message is not atomic and the lettuce check is
 done at the exact time only part of the message is not output?

 Anyway, it is some kind of race condition, as it obviously happens only
 sometimes.

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