On 27/02/2015 15:01, Mark Thomas wrote:
> On 27/02/2015 14:42, Christopher Schultz wrote:
>> On 2/27/15 7:00 AM, Mark Thomas wrote:
>>> There is also an issue with APR on Linux that I can reproduce (with some
>>> code changes) that triggers a crash every couple of runs.
>>
>> Next time is happen
2015-02-27 13:00 GMT+01:00 Mark Thomas :
> Another update. I think I am getting close to being able to commit these
> changes[1].
>
> The current status is:
> - NIO appears to pass on Windows, OSX and Linux
> - APR appears to pass on OSX and Linux
> - APR unknown on Windows
> - NIO2 appears to pas
On 27/02/2015 14:42, Christopher Schultz wrote:
> Mark,
>
> On 2/27/15 7:00 AM, Mark Thomas wrote:
>> Another update. I think I am getting close to being able to commit these
>> changes[1].
>>
>> The current status is:
>> - NIO appears to pass on Windows, OSX and Linux
>> - APR appears to pass on
Mark,
On 2/27/15 7:00 AM, Mark Thomas wrote:
> Another update. I think I am getting close to being able to commit these
> changes[1].
>
> The current status is:
> - NIO appears to pass on Windows, OSX and Linux
> - APR appears to pass on OSX and Linux
> - APR unknown on Windows
> - NIO2 appears t
Another update. I think I am getting close to being able to commit these
changes[1].
The current status is:
- NIO appears to pass on Windows, OSX and Linux
- APR appears to pass on OSX and Linux
- APR unknown on Windows
- NIO2 appears to pass on OSX and Linux
- NIO2 hanging on Windows
I say "appe
On 26/02/2015 21:58, Christopher Schultz wrote:
> Mark,
>
> On 2/23/15 4:16 AM, Mark Thomas wrote:
>> Given that it is my changes that have triggered the problems I think I
>> have a responsibility to fix them (and intend to do so over) but I'm not
>> going to say no if anyone wants to pitch in. T
Mark,
On 2/23/15 4:16 AM, Mark Thomas wrote:
> Given that it is my changes that have triggered the problems I think I
> have a responsibility to fix them (and intend to do so over) but I'm not
> going to say no if anyone wants to pitch in. Therefore, I'm starting
> this thread so that we can co-or
On 26/02/2015 17:34, Rémy Maucherat wrote:
> 2015-02-26 17:40 GMT+01:00 Mark Thomas :
>
>> Better, certainly.
>>
>> NIO tests pass on Windows, Linux and OSX.
>>
>
> Very good !
>
>
>> I've found a bug in NIO2 + SSL that is fairly common on Linux/OSX that I
>> have fixed and am re-running the te
2015-02-26 17:40 GMT+01:00 Mark Thomas :
> Better, certainly.
>
> NIO tests pass on Windows, Linux and OSX.
>
Very good !
> I've found a bug in NIO2 + SSL that is fairly common on Linux/OSX that I
> have fixed and am re-running the tests.
>
Aw, *another* one ?
>
> I haven't really looked at A
On 26/02/2015 12:25, Rémy Maucherat wrote:
> 2015-02-26 11:42 GMT+01:00 Mark Thomas :
>
>> What I have at the moment is at:
>> https://github.com/markt-asf/tomcat/tree/markt-trunk
>>
>> I'm currently running the unit tests.
>>
> Looking good.
Better, certainly.
NIO tests pass on Windows, Linux a
2015-02-26 11:42 GMT+01:00 Mark Thomas :
> What I have at the moment is at:
> https://github.com/markt-asf/tomcat/tree/markt-trunk
>
> I'm currently running the unit tests.
>
> Looking good.
Rémy
On 25/02/2015 19:32, Rémy Maucherat wrote:
> 2015-02-25 19:36 GMT+01:00 Mark Thomas :
>
>> I was planning on waiting until the build was stable but given that:
>> - read/write concurrency is at the root of a lot of these issues
>> - only WebSocket should be using it now in trunk
>> - the plan is t
2015-02-25 19:36 GMT+01:00 Mark Thomas :
> I was planning on waiting until the build was stable but given that:
> - read/write concurrency is at the root of a lot of these issues
> - only WebSocket should be using it now in trunk
> - the plan is to refactor WebSocket to remove it
>
> I'm going to
On 25/02/2015 14:31, Rémy Maucherat wrote:
> 2015-02-24 16:33 GMT+01:00 Mark Thomas :
>
>> On 24/02/2015 13:10, Rémy Maucherat wrote:
>>> I'm having issues with the write timeout tests in
>>> TestWsWebSocketContainer, which made me do some changes since there are
>>> still things I don't understan
2015-02-24 16:33 GMT+01:00 Mark Thomas :
> On 24/02/2015 13:10, Rémy Maucherat wrote:
> > I'm having issues with the write timeout tests in
> > TestWsWebSocketContainer, which made me do some changes since there are
> > still things I don't understand:
>
> These appear to be OK for me at the momen
On 24/02/2015 13:10, Rémy Maucherat wrote:
> I'm having issues with the write timeout tests in
> TestWsWebSocketContainer, which made me do some changes since there are
> still things I don't understand:
These appear to be OK for me at the moment with NIO and NIO2 but the
very nature of timing iss
2015-02-24 10:01 GMT+01:00 Mark Thomas :
> Progress is being made.
>
> TestWsWebSocketContainer.testMaxMessageSize04() is fixed. I do want to
> come back to exactly how/if flushing is performed on
> ServletOutputStream.close() but I plan on parking that until the other
> failures are fixed.
>
> I'
On 24/02/2015 09:01, Mark Thomas wrote:
> Progress is being made.
>
> TestWsWebSocketContainer.testMaxMessageSize04() is fixed. I do want to
> come back to exactly how/if flushing is performed on
> ServletOutputStream.close() but I plan on parking that until the other
> failures are fixed.
>
> Ne
On 24/02/2015 10:22, Rainer Jung wrote:
> Am 24.02.2015 um 10:01 schrieb Mark Thomas:
>
>> On a related topic the Gump OpenSSL tests are still failing. They pass
>> when run directly from the command line on vmgump.a.o. I can't come up
>> with a better idea than adding some debugging to the tests.
Am 24.02.2015 um 10:01 schrieb Mark Thomas:
On a related topic the Gump OpenSSL tests are still failing. They pass
when run directly from the command line on vmgump.a.o. I can't come up
with a better idea than adding some debugging to the tests.
I installed OpenSSL master (current snapshot) lo
Progress is being made.
TestWsWebSocketContainer.testMaxMessageSize04() is fixed. I do want to
come back to exactly how/if flushing is performed on
ServletOutputStream.close() but I plan on parking that until the other
failures are fixed.
Next on my list is TestUpgrade.testMessagesBlocking(). I a
On 23/02/2015 10:40, Rémy Maucherat wrote:
> 2015-02-23 10:16 GMT+01:00 Mark Thomas :
>
>> Given that it is my changes that have triggered the problems I think I
>> have a responsibility to fix them (and intend to do so over) but I'm not
>> going to say no if anyone wants to pitch in. Therefore, I
2015-02-23 10:16 GMT+01:00 Mark Thomas :
> Given that it is my changes that have triggered the problems I think I
> have a responsibility to fix them (and intend to do so over) but I'm not
> going to say no if anyone wants to pitch in. Therefore, I'm starting
> this thread so that we can co-ordina
Given that it is my changes that have triggered the problems I think I
have a responsibility to fix them (and intend to do so over) but I'm not
going to say no if anyone wants to pitch in. Therefore, I'm starting
this thread so that we can co-ordinate work on fixing the various
failures being repor
24 matches
Mail list logo