On 19/10/2015 13:43, Konstantin Kolinko wrote: > 2015-10-19 14:16 GMT+03:00 Mark Thomas <ma...@apache.org>: >> On 17/10/2015 15:54, Konstantin Kolinko wrote: >>> 2015-10-17 10:48 GMT+03:00 Bill Barker <billbar...@apache.org>: >>>> To whom it may engage... >>>> >>>> This is an automated request, but not an unsolicited one. For >>>> more information please visit http://gump.apache.org/nagged.html, >>>> and/or contact the folk at gene...@gump.apache.org. >>>> >>>> Project tomcat-trunk-test-apr has an issue affecting its community >>>> integration. >>>> This issue affects 1 projects, >>>> and has been outstanding for 23 runs. >>>> The current state of this project is 'Failed', with reason 'Build Timed >>>> Out'. >>>> For reference only, the following projects are affected by this: >>>> - tomcat-trunk-test-apr : Tomcat 9.x, a web server implementing the >>>> Java Servlet 4.0, >>>> ... >>>> >>>> >>>> Full details are available at: >>>> >>>> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test-apr/index.html >>>> >>>> That said, some information snippets are provided here. >>>> >>>> The following annotations (debug/informational/warning/error messages) >>>> were provided: >>>> -DEBUG- Dependency on commons-daemon exists, no need to add for property >>>> commons-daemon.native.src.tgz. >>>> -DEBUG- Dependency on commons-daemon exists, no need to add for property >>>> tomcat-native.tar.gz. >>>> -INFO- Failed with reason build timed out >>>> -INFO- Project Reports in: >>>> /srv/gump/public/workspace/tomcat-trunk/output/logs-APR >>>> -INFO- Project Reports in: >>>> /srv/gump/public/workspace/tomcat-trunk/output/test-tmp-APR/logs >>>> -WARNING- No directory >>>> [/srv/gump/public/workspace/tomcat-trunk/output/test-tmp-APR/logs] >>>> >>>> >>>> >>>> The following work was performed: >>>> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test-apr/gump_work/build_tomcat-trunk_tomcat-trunk-test-apr.html >>>> Work Name: build_tomcat-trunk_tomcat-trunk-test-apr (Type: Build) >>>> Work ended in a state of : Failed >>>> Elapsed: 1 hour 1 sec >>> >>> From stdout output, testing started at 06:49 >>> The tail of stdout is cited below. The times are around 07:11. The >>> last test name mentioned is >>> >>> Running org.apache.coyote.http11.filters.TestChunkedInputFilter >>> ... >>> org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case >>> [testChunkSizeLong] >>> >>> Apparently it hung after that and was killed 35 minutes later. >> >> The last few runs have consistently failed at the same place. >> >> Can anyone reproduce this locally? (I haven't tried yet.) > > > An idea: maybe add a StuckThreadDetectionValve into configuration of that > test? > My expectation is that it will print a stacktrace of the hanging > thread so that we have a clue where the hang is.
No need. I can repeat this locally (OSX, APR 1.6.0, OpenSSL 1.0.2d, native 1.2.0-dev). The problem is occurring when trying to swallow the input that isn't there. I want to go back through the mail archives to see if I can find when this started to fail. Hopefully that will point me in the direction of the change that triggered this. > Trunk/Nio2 today failed at > > [concat] Testsuites with failed tests: > [concat] TEST-org.apache.coyote.http2.TestHttp2Section_5_3.NIO2.txt > [concat] > TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.NIO2.txt > > > In TEST-org.apache.coyote.http2.TestHttp2Section_5_3.NIO2: > > Testcase: testWeighting took 10.618 sec > FAILED > Larger than expected body: [21-Body-5 OK. I think that is a problem with the test. I probably have some more work to do on that one. > In TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.NIO2: That isn't particularly new is it? I think we have been seeing failures with that on and off for a while. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
