BIND 10 #2888: msgq unittest failure on OpenBSD
BIND 10 Development
do-not-reply at isc.org
Mon Apr 1 01:14:42 UTC 2013
#2888: msgq unittest failure on OpenBSD
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: defect | Status: new
Priority: very high | Milestone: Next-
Component: msgq | Sprint-Proposed
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: Core | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:1 vorner]:
> As is commented in the test source, the goal is on the border between
unit
> tests and system tests. It does test specific behaviour, but of the
whole msgq.
> There's a lot of recv/send handling that is/(or at least was some time
ago)
> broken and it is needed to check it.
>
> It seemed easier to write it as unit test than lettuce test. In lettuce,
it
> would be easier to start the msgq, but then, keeping a connection open
and
> sending and receiving data across it would be hell.
I'm not convinced that abusing unit tests this way is the best
approach, but as the existing tests already passed the review-merge
process I won't fight against that at this moment.
The most important and urgent issue is to fix the occasional
failures. If we can do this by tweaking the test case I'm okay with
it for the purpose of this ticket. I reserve the opinion of
revisiting the approach itself, though.
BTW, this doesn't seem to be OpenBSD specific.
--
Ticket URL: <http://bind10.isc.org/ticket/2888#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list