BIND 10 #2888: msgq unittest failure on OpenBSD
BIND 10 Development
do-not-reply at isc.org
Tue Mar 26 22:02:22 UTC 2013
#2888: msgq unittest failure on OpenBSD
-------------------------------------+-------------------------------------
Reporter: | Owner:
jinmei | Status: new
Type: | Milestone: Next-Sprint-
defect | Proposed
Priority: very | Keywords:
high | Sensitive: 0
Component: msgq | Sub-Project: Core
CVSS Scoring: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
I confirmed this can be reproducible.
http://git.bind10.isc.org/~tester/builder//BIND10/20130326104118-OpenBSD5-amd64/logs/unittests.out
Sometimes it succeeded, so it may be a timing issue. BTW: I think we
should try to avoid using different processes for unit tests. I'm not
sure that's a background reason for it, but in general that's a source
of troubles.
--
Ticket URL: <http://bind10.isc.org/ticket/2888>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list