Your message dated Thu, 23 Oct 2014 14:56:44 -0400
with message-id
<cabjrnbf539232jrbbzovcd4x6uioskaxf+t55lu22-0pkme...@mail.gmail.com>
and subject line
has caused the Debian Bug report #759394,
regarding nanomsg doesn't handle blocked reads correctly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
759394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759394
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libnanomsg0
Version: 0.4~beta+dfsg-1
Control: block 756350 by -1
Control: affects -1 + libnanomsg-raw-perl
Control: forwarded -1 https://github.com/nanomsg/nanomsg/issues/305
Control: thanks
There appears to be a bug in nanomsg which causes a failure to randomly
occur in the t/thread.t test in NanoMsg::Raw that is related to the
failure to handle EAGAIN in the nn_efd_unsignal extraction of all
signals from the eventfd.
Sincerely,
--
Harlan Lieberman-Berg
~hlieberman
--- End Message ---
--- Begin Message ---
After investigating this more and recreating the Perl test in C, I believe
that this is not actually a bug, and the problem is in the Perl XS code
itself.
Sincerely,
--
Harlan Lieberman-Berg
~hlieberman
--- End Message ---
