BIND 10 #2670: "A deadlock might be detected" failure on NetBSD
BIND 10 Development
do-not-reply at isc.org
Thu Jan 31 07:03:19 UTC 2013
#2670: "A deadlock might be detected" failure on NetBSD
-------------------------------------+-------------------------------------
Reporter: naokikambe | Owner:
Type: defect | jinmei
Priority: medium | Status:
Component: statistics | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20130205
Sub-Project: DNS | Resolution:
Estimated Difficulty: 0 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:5 naokikambe]:
> I'd like to stop working for it by guessing randomly. I would not have
any other good idea soon. So should we pull this ticket out of the current
sprint? I would remove the branch from the repository if so.
At this point I think we should close this ticket as "wontfix", and
create a separate new ticket for a complete solution.
BTW, even if it may be quite specific to NetBSD (although I sometimes
see similar failure on my OSX laptop), for a "complete" solution I'd
like to suggest getting rid of threads. I believe we should be able
to introduce proper mock classes for most, if not all, of the tests
without requiring inter-process communication and blocking operations.
Threads are too tricky for primitive things like unit tests, and a
perfect recipe for disaster.
--
Ticket URL: <http://bind10.isc.org/ticket/2670#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list