On 01/09/2012 09:29, Mark Thomas wrote:
> On 31/08/2012 23:06, Mark Thomas wrote:
>> On 31/08/2012 17:06, Mark Thomas wrote:
>>> I am seeing a repeatable failure of a Comet test (stop
>>> connector) with APR on Linux. I want to take a look at this before
>>>
On 31/08/2012 23:06, Mark Thomas wrote:
> On 31/08/2012 17:06, Mark Thomas wrote:
>> I am seeing a repeatable failure of a Comet test (stop
>> connector) with APR on Linux. I want to take a look at this before
>> tagging 7.0.30.
>
> Unit tests now passing consist
On 31/08/2012 17:06, Mark Thomas wrote:
> I am seeing a repeatable failure of a Comet test (stop
> connector) with APR on Linux. I want to take a look at this before
> tagging 7.0.30.
Unit tests now passing consistently on my local Linux and Windows
systems (as well as buildbot).
I a
rMemoryLeak#testTimerThreadLeak
>>
>> Tested BIOxNIOxAPR (native 1.1.24) with JDK 6u34 32-bit on WinXP
>
> Thanks for that confirmation.
>
> I believe we are now good to tag 7.0.30. I'll run the TCKs
On 28/08/2012 02:24, Konstantin Kolinko wrote:
> 2012/8/27 Mark Thomas :
>> Hi,
>>
>> I have all the open bugs fixed for 7.0.x with the exception of BZ53469
>> that is pending input from the Servlet EG before a final fix (if any) is
>> applied.
>>
>> I have a few other bits and pieces I want to do
2012/8/27 Mark Thomas :
> Hi,
>
> I have all the open bugs fixed for 7.0.x with the exception of BZ53469
> that is pending input from the Servlet EG before a final fix (if any) is
> applied.
>
> I have a few other bits and pieces I want to do before I tag 7.0.30 but
> (assuming no more bugs are ope
Dear Mark,
would you mind to take a look at BZ51496?
As you pointed out your focus is to get open bugs fixed for 7.0.30.
Well, this is not a bug, but an enhancement and to be honest I don’t
know if it is planned to consider enhancements for minor releases as
well. I proposed a patch.
Thank you.
Hi,
I have all the open bugs fixed for 7.0.x with the exception of BZ53469
that is pending input from the Servlet EG before a final fix (if any) is
applied.
I have a few other bits and pieces I want to do before I tag 7.0.30 but
(assuming no more bugs are opened) I anticipate tagging in the next