BIND 10 #1938: why ZONEMGR_UNKNOWN_ZONE_NOTIFIED ?
BIND 10 Development
do-not-reply at isc.org
Fri Mar 22 16:09:48 UTC 2013
#1938: why ZONEMGR_UNKNOWN_ZONE_NOTIFIED ?
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | jinmei
Priority: high | Status:
Component: secondary | reviewing
manager | Milestone:
Keywords: | Sprint-20130402
Sensitive: 0 | Resolution:
Sub-Project: DNS | CVSS Scoring:
Estimated Difficulty: 5 | Defect Severity:
Total Hours: 0 | Medium
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:24 jelte]:
> OK this approach seems to work :)
Okay, good.
> There is one final thing, not sure if this is the one you meant, but I
think xfrin_notify_handling.feature:168 should be 'not
XFRIN_TRANSFER_SUCCESS' instead of 'not XFRIN_TRANSFER_STARTED'
>
> {{{
> - Then wait for bind10 stderr message
XFRIN_XFR_TRANSFER_PROTOCOL_VIOLATION not XFRIN_XFR_TRANSFER_STARTED
> + Then wait for bind10 stderr message
XFRIN_XFR_TRANSFER_PROTOCOL_VIOLATION not XFRIN_XFR_TRANSFER_SUCCESS
> }}}
Ah, right. It looks like a typo existing before this branch, but now
that we stop using 'new' here, it could make the test fail (actually,
I suspect it would always make it fail; I'm not sure why I didn't
notice it). I've made this change and merged the branch.
Now closing the ticket.
--
Ticket URL: <http://bind10.isc.org/ticket/1938#comment:25>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list