Thanks. Another option in these cases is to mark the test TODO and
gracefully ignore it's failure, but this fix is fine in the interim.
On Oct 15, 2016 10:35 AM, "Yann Ylavic" wrote:
> On Sat, Oct 15, 2016 at 4:30 PM, Yann Ylavic wrote:
> > On Sat,
On Sat, Oct 15, 2016 at 4:30 PM, Yann Ylavic wrote:
> On Sat, Oct 15, 2016 at 4:20 PM, Yann Ylavic wrote:
>> On Sat, Oct 15, 2016 at 3:10 PM, Jim Jagielski wrote:
>>> Anyone...? Any ideas??
>>
>> This seems to come from r1756746,
On Sat, Oct 15, 2016 at 4:30 PM, Yann Ylavic wrote:
> On Sat, Oct 15, 2016 at 4:20 PM, Yann Ylavic wrote:
>> On Sat, Oct 15, 2016 at 3:10 PM, Jim Jagielski wrote:
>>> Anyone...? Any ideas??
>>
>> This seems to come from r1756746,
On Sat, Oct 15, 2016 at 4:20 PM, Yann Ylavic wrote:
> On Sat, Oct 15, 2016 at 3:10 PM, Jim Jagielski wrote:
>> Anyone...? Any ideas??
>
> This seems to come from r1756746, which I think should be trunk
> specific (for now).
The attached works for me..
On Sat, Oct 15, 2016 at 3:10 PM, Jim Jagielski wrote:
> Anyone...? Any ideas??
This seems to come from r1756746, which I think should be trunk
specific (for now).
Anyone...? Any ideas??
> On Oct 11, 2016, at 12:34 PM, Jim Jagielski wrote:
>
> On HEAD of httpd-2.4, the test framework fails on headers.t:
>
> header: [FooBar] vs [Foo Bar]
> # testing : compare header Hello value
> # expected: 'Foo Bar'
> # received: 'Foo