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):

 This commit log message also includes some extra info:
 {{{
 commit 85f9295ccf26f69cd6e7e30a9022b57ea9e9efda
 Author: Mukund Sivaraman <muks@>
 Date:   Wed Jan 29 12:33:07 2014 +0530

     [3301] Wait for new message XFRIN log messages

     This reverts changes that were made in commit
     199beea87baee4dd3d4339ec20c32d0d2cb47f40. It seems that commit removed
     the wait for a "new" logged message, and introduced the regression in

     Without waiting for a new log message, the check matches log messages
     that were generated by initial AXFR during startup of the secondary
     ("bind10") instance.
 }}}

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