BIND 10 #1704: log output mixed
BIND 10 Development
do-not-reply at isc.org
Sun Jun 3 20:57:49 UTC 2012
#1704: log output mixed
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: muks
Type: | Status: reviewing
defect | Milestone:
Priority: | Sprint-20120612
medium | Resolution:
Component: | Sensitive: 0
logging | Sub-Project: Core
Keywords: | Estimated Difficulty: 15
Defect Severity: N/A | Total Hours: 12.25
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by muks):
Replying to [comment:65 jinmei]:
> Hmm, it does not necessarily have to be a fixture, but, technically,
> adding cleanup code in the end of a test case is fragile because we
> might skip it due to ASSERT_xx failure (and the missing cleanup might
> cause unrelated false positives). Also, it's more error prone because
> we could easily add another similar test case but forgetting the
> cleanup. For the distcheck case you explained, the first reason
> doesn't matter because the check will fail anyway, but in general I
> prefer keeping it as safe as possible.
That does make good sense for cleanup. We should update it at some point.
--
Ticket URL: <http://149.20.48.40/ticket/1704#comment:68>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list