On Fri, May 14, 2010 at 10:51 PM, Blair Zajac <blair_at_orcaware.com> wrote:
> On 05/14/2010 05:32 AM, Lieven Govaerts wrote:
>>
>> On Thu, May 13, 2010 at 11:03 PM, Blair Zajac<blair_at_orcaware.com> wrote:
>>>
>>> On 05/13/2010 11:55 AM, Greg Stein wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I'm pleased to announce the serf 0.4.0 release!
>>>>
>>>> Quick summary of changes in this release:
>>>>
>>>> Provide authn framework, supporting Basic, Digest, Kerberos (SSPI,
>>>> GSS),
>>>> along with proxy authn using Basic or Digest
>>>> Added experimental listener framework, along with test_server.c
>>>> Improvements and fixes to SSL support, including connection setup
>>>> changes
>>>> Experimental support for unrequested, arriving ("async") responses
>>>> Experimental BWTP support using the async arrival feature
>>>> Headers are combined on read (not write), to ease certian classes of
>>>> parsing
>>>> Experimental feature on aggregate buckets for a callback-on-empty
>>>> Fix the bucket allocator for when APR is using its pool debugging
>>>> features
>>>> Proxy support in the serf_get testing utility
>>>> Fix to include the port number in the Host header
>>>> serf_get propagates errors from the response, instead of aborting
>>>> (Issue
>>>> 52)
>>>> Added serf_lib_version() for runtime version tests
>>>
>>> I just updated the serf package in MacPorts.
>>>
>>> But I'm getting these failures in the test suite:
>>>
>>> There were 5 failures:
>>> 1) test_serf_closed_connection: test/test_context.c:444: expected<0> but
>>> was<20014>
>>> 2) test_serf_setup_proxy: test/test_context.c:512: expected<0> but
>>> was<48>
>>> 3) test_keepalive_limit_one_by_one: test/test_context.c:700: expected<0>
>>> but was<48>
>>> 4) test_keepalive_limit_one_by_one_and_burst: test/test_context.c:860:
>>> expected<0> but was<48>
>>> 5) test_serf_progress_callback: test/test_context.c:980: expected<0> but
>>> was<48>
>>>
>>
>> This looks like issues 51 and 54 [1]. Can you test the patch attached
>> to issue 51 to see if that solves your problem? It didn't solve it for
>> me, atleast, not consistently. Make sure you run the testsuite a few
>> times, as the results may differ.
>>
>> I believe this to be an issue in the test suite, not in serf itself.
>
> Lieven,
>
> I ran the test suite 6 times on 10.6 and it passed successfully all times.
>
Just to be clear, this was after you used the patch from issue 51?
In that case, I'll apply it and see what's wrong with serf on my mac.
Lieven
Received on 2010-05-15 13:43:23 CEST