[bind10-dev] msgq error on write, was Re: failed systest

[Shane Kerr]

Jeremy,

On Thu, 2011-10-06 at 19:29 -0500, Jeremy C. Reed wrote:
> On Thu, 6 Oct 2011, BIND 10 Tests wrote:
> 
> > Date: Thu,  6 Oct 2011 23:10:01 +0000 (UTC)
> > From: BIND 10 Tests <tester at isc.org>
> > To: bind10-team at lists.isc.org
> > Subject: failed systest
> > 
> > http://git.bind10.isc.org/~tester/builder//BIND10-systest/20111006225719-MacOS/logs/systest.out
> > 
> > http://git.bind10.isc.org/~tester/builder//builder.html
> 
> Looks like msgq crashed:
> 
> http://git.bind10.isc.org/~jreed/bindctl-bind10.run.txt
> 
> Also see
> http://git.bind10.isc.org/~jreed/glue-bind10.run.txt
> this had errors but the overall systest for it resulted in:
> R:PASS
> That should be fixed.
> 
> 
> I think highest debug level should be used for this output.

We've come a long way since ticket #29:

http://bind10.isc.org/ticket/29

;)

Anyway, this is caused because one of the msgq clients has exited and
msgq is trying to write to that client. This is the sort of error that
makes us want to replace msgq.

We have a ticket for this:

http://bind10.isc.org/ticket/1180

Since the error is relatively easy to fix and we've seen it a couple of
times, I'll put it on the next-sprint-proposed milestone. (The tricky
part is that to fix it properly we'd need tests, but msgq is deliciously
free of any tests. Since we want to replace msgq, I think that we can
just hack it and add code that should fix the problem, hopefully.)

--
Shane