You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mark Thomas <ma...@apache.org> on 2014/08/12 14:42:54 UTC
Tomcat for 8.0.next
It has been a while since my aborted attempt at the last 8.0.x release
and we have quite a few additional changes so I intend to start a 8.0.x
release shortly.
I'm starting to run the unit tests on the usual platforms (OSX, Win64,
Linux64) now and - assuming they all pass - I'll tag 8.0.11 once the
tests complete. I may still tag if we see some failures (e.g. in NIO2)
but I'll look at the on a case by case basis.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Tomcat for 8.0.next
Posted by Mark Thomas <ma...@apache.org>.
On 12/08/2014 13:42, Mark Thomas wrote:
> It has been a while since my aborted attempt at the last 8.0.x release
> and we have quite a few additional changes so I intend to start a 8.0.x
> release shortly.
>
> I'm starting to run the unit tests on the usual platforms (OSX, Win64,
> Linux64) now and - assuming they all pass - I'll tag 8.0.11 once the
> tests complete. I may still tag if we see some failures (e.g. in NIO2)
> but I'll look at the on a case by case basis.
Unsurprisingly, I got distracted. Trying this again now...
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Tomcat for 8.0.next
Posted by Konstantin Kolinko <kn...@gmail.com>.
2014-08-12 17:08 GMT+04:00 Konstantin Kolinko <kn...@gmail.com>:
> 2014-08-12 16:59 GMT+04:00 Rémy Maucherat <re...@apache.org>:
>> 2014-08-12 14:42 GMT+02:00 Mark Thomas <ma...@apache.org>:
>>
>>> I may still tag if we see some failures (e.g. in NIO2)
>>> but I'll look at the on a case by case basis.
>>>
>>> From what I understand, any problem would be a regression, which means it
>> would be a good plan to investigate before tagging.
>> Other than that, +1
>
> Gump shows repeatable failures with NIO2 for many days (I think that
> started since OS update on vmgump).
>
>
>> [junit] Test org.apache.catalina.nonblocking.TestNonBlockingAPI FAILED
>
> Testsuite: org.apache.catalina.nonblocking.TestNonBlockingAPI
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 27.534 sec
> ------------- Standard Error -----------------
> (a lot of lines - omitting...)
> ------------- ---------------- ---------------
>
> Testcase: testBug55438NonBlockingReadWriteEmptyRead took 2 sec
> Testcase: testNonBlockingRead took 2.172 sec
> Testcase: testNonBlockingWriteError took 14.015 sec
> FAILED
> Error listener should have been invoked.
> junit.framework.AssertionFailedError: Error listener should have been invoked.
> at org.apache.catalina.nonblocking.TestNonBlockingAPI.testNonBlockingWriteError(TestNonBlockingAPI.java:347)
>
> Testcase: testNonBlockingReadIgnoreIsReady took 1.661 sec
> Testcase: testNonBlockingWrite took 7.672 sec
>
For a record, tests with APR connector on Gump are failing in
TestNonBlockingAPI
in exactly the same way. All other tests in whole testsuite complete
successfully.
(....)
Testcase: testNonBlockingWriteError took 10.732 sec
FAILED
Error listener should have been invoked.
junit.framework.AssertionFailedError: Error listener should have been invoked.
at org.apache.catalina.nonblocking.TestNonBlockingAPI.testNonBlockingWriteError(TestNonBlockingAPI.java:347)
(...)
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test-apr/gump_file/TEST-org.apache.catalina.nonblocking.TestNonBlockingAPI.APR.txt.html
Thanks to Remy's update to the test in r1617734, the NIO2 connector is
no longer failing there.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Tomcat for 8.0.next
Posted by Rémy Maucherat <re...@apache.org>.
2014-08-12 15:08 GMT+02:00 Konstantin Kolinko <kn...@gmail.com>:
> > [junit] Test org.apache.catalina.nonblocking.TestNonBlockingAPI FAILED
>
> Testsuite: org.apache.catalina.nonblocking.TestNonBlockingAPI
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 27.534 sec
> ------------- Standard Error -----------------
> (a lot of lines - omitting...)
> ------------- ---------------- ---------------
>
> Testcase: testBug55438NonBlockingReadWriteEmptyRead took 2 sec
> Testcase: testNonBlockingRead took 2.172 sec
> Testcase: testNonBlockingWriteError took 14.015 sec
> FAILED
> Error listener should have been invoked.
> junit.framework.AssertionFailedError: Error listener should have been
> invoked.
> at
> org.apache.catalina.nonblocking.TestNonBlockingAPI.testNonBlockingWriteError(TestNonBlockingAPI.java:347)
>
Yes, but this is actually not new, since I had it fail for me once in a
while locally. So it seems less occasional now in gump. It looked to me
like a timing issue (the NIO2 is a bit different from the other connector
for this sort of errors) and I didn't care much about it.
Rémy
Re: Tomcat for 8.0.next
Posted by Konstantin Kolinko <kn...@gmail.com>.
2014-08-12 16:59 GMT+04:00 Rémy Maucherat <re...@apache.org>:
> 2014-08-12 14:42 GMT+02:00 Mark Thomas <ma...@apache.org>:
>
>> I may still tag if we see some failures (e.g. in NIO2)
>> but I'll look at the on a case by case basis.
>>
>> From what I understand, any problem would be a regression, which means it
> would be a good plan to investigate before tagging.
> Other than that, +1
Gump shows repeatable failures with NIO2 for many days (I think that
started since OS update on vmgump).
> [junit] Test org.apache.catalina.nonblocking.TestNonBlockingAPI FAILED
Testsuite: org.apache.catalina.nonblocking.TestNonBlockingAPI
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 27.534 sec
------------- Standard Error -----------------
(a lot of lines - omitting...)
------------- ---------------- ---------------
Testcase: testBug55438NonBlockingReadWriteEmptyRead took 2 sec
Testcase: testNonBlockingRead took 2.172 sec
Testcase: testNonBlockingWriteError took 14.015 sec
FAILED
Error listener should have been invoked.
junit.framework.AssertionFailedError: Error listener should have been invoked.
at org.apache.catalina.nonblocking.TestNonBlockingAPI.testNonBlockingWriteError(TestNonBlockingAPI.java:347)
Testcase: testNonBlockingReadIgnoreIsReady took 1.661 sec
Testcase: testNonBlockingWrite took 7.672 sec
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Tomcat for 8.0.next
Posted by Rémy Maucherat <re...@apache.org>.
2014-08-12 14:42 GMT+02:00 Mark Thomas <ma...@apache.org>:
> I may still tag if we see some failures (e.g. in NIO2)
> but I'll look at the on a case by case basis.
>
> From what I understand, any problem would be a regression, which means it
would be a good plan to investigate before tagging.
Other than that, +1
Rémy