What steps will reproduce the problem?
1. placed the attached prove test (udpBinary.t) into <WORKSPACE_ROOT>/t
2. run the test
3. note that 'select' operations times out while waiting for I/O from the
server and then test
hangs
smacky:memcached elambert$ prove t/udpBinary.t
t/udpBinary....ok 1/12
# Failed test 'got readability'
# in t/udpBinary.t at line 120.
t/udpBinary....NOK 2^C
(NOTE, the attached test is not really ready for prime time as basically all it
does is check that
server has i/o to send back and then reads the i/o if there is some. The test
will be improved to
do more, so probably should not be added to the source tree for the time
being).
What is the expected output? What do you see instead?
The test should not fail waiting on I/O from the server, the test should not
hang.
(Tagging this as high priority since the 1.3.2 release is supposed to be the
official binary
protocol release and probably best that binaryUDP work since ASCII udp works,
but clearly this is
not a regression --since binary was not avail in the 1.2.6-- and as such I
would not fight
downgrading the priority)
Original issue reported on code.google.com by eric.d.l...@gmail.com on 25 Mar 2009 at 1:53
Original issue reported on code.google.com by
eric.d.l...@gmail.com
on 25 Mar 2009 at 1:53Attachments: