BIND 10 #3301: lettuce failure in Scenario: Handle incoming notify (XFR request rejected) --- assert found != not_message, line

[BIND 10 Development]

#3301: lettuce failure in Scenario: Handle incoming notify (XFR request rejected)
--- assert found != not_message, line
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:  muks
                Type:  defect        |                       Status:
            Priority:  medium        |  reviewing
           Component:  tests         |                    Milestone:
            Keywords:                |  bind10-1.2-release-freeze
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by muks):

 Replying to [comment:5 kean]:
 > I noticed the removal of the following comment:
 > {{{
 >     # From this point we can't reliably 'wait for new' because the
 ordering
 >     # of logs from different processes is unpredictable.  But these
 >     # should be okay in this case.
 > }}}
 >
 > and then you use "wait for new". In 2 other places a comment saying they
 cant use wait for new was also changed. However I didn't see any changes
 in the harness itself that would change the "wait for new" behaviour. Were
 those old comments simply inaccurate? Some of them look like it was just
 cut-n-paste so they may well have been. If that is the case then this
 looks fine, please go ahead and merge and close.

 The regression was introduced during a merge conflict resolution commit,
 where these "wait for new" statements were replaced (and it seems without
 any review). However these are required, and the log messages in these
 lettuce scenarios arrive in deterministic order.

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