[Christoph Egger] > There were 7 failures: > 1) test_serf_connection_request_create: ../test/test_context.c:166: expected > <0> but was <22> > 2) test_serf_connection_priority_request_create: ../test/test_context.c:265: > expected <0> but was <22> > 3) test_serf_closed_connection: ../test/test_context.c:404: expected <0> but > was <22> > 4) test_serf_setup_proxy: ../test/test_context.c:506: expected <0> but was > <22> > 5) test_keepalive_limit_one_by_one: ../test/test_context.c:657: expected <0> > but was <22> > 6) test_keepalive_limit_one_by_one_and_burst: ../test/test_context.c:811: > expected <0> but was <22> > 7) test_serf_progress_callback: ../test/test_context.c:933: expected <0> but > was <22>
Thanks - I saw those. serf on Linux was FTBFS in pretty much exactly the same way until I kludged the testsuite to connect to ip6-localhost instead of localhost. There was some confusion about trying to use the 'localhost' IP on an IPv6 socket. I don't fully understand it myself. But if upstream can resolve it at some point, it will probably resolve this failure too. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
