2012/3/7 Mark Thomas <ma...@apache.org>: > On 06/03/2012 21:27, build...@apache.org wrote: >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2816 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1297717 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 > > Drat. The Comet unit tests are still failing. I had hoped we had fixed that. > > We really need the Gump run to fail so we have access to the full logs > to better understand which test is failing and why. Either that or a way > to extract the logs from buildbot. Hmm. I probably have access to that > machine. I'll go and have a look. >
One more: Gump MacOS server fails the Comet tests in trunk and 7.0.x See http://tomcat.apache.org/ci.html#Gump then look for "Adam" http://adam.apache.org/gump/tomcat-trunk/tomcat-trunk-test/gump_file/TEST-org.apache.catalina.comet.TestCometProcessor.NIO.txt.html The trunk and tc7.0.x runs have the same failure - the stop test fails: [[[ Testcase: testCometConnectorStop took 13.144 sec FAILED Comet END event not received junit.framework.AssertionFailedError: Comet END event not received at org.apache.catalina.comet.TestCometProcessor.testCometConnectorStop(TestCometProcessor.java:325) ]]] Log: [[[ Mar 6, 2012 11:43:24 AM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-6"] Mar 6, 2012 11:43:24 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector INFO: Using a shared selector for servlet write/read Mar 6, 2012 11:43:24 AM org.apache.catalina.core.StandardService startInternal INFO: Starting service Tomcat Mar 6, 2012 11:43:24 AM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/8.0.0-dev Mar 6, 2012 11:43:24 AM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-auto-6"] Mar 6, 2012 11:43:27 AM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-6"] Mar 6, 2012 11:43:37 AM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-6"] Mar 6, 2012 11:43:37 AM org.apache.catalina.comet.TestCometProcessor testCometConnectorStop SEVERE: Status: WriterThread exception: null ReaderThread exception: java.net.SocketTimeoutException: Read timed out Last message: [Client: READ: 4 bytes] Last response line: [Client: READ: 4 bytes] Last comet event: [READ] Mar 6, 2012 11:43:37 AM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Tomcat ]]] It is likely that Tomcat stops without delivering END event to the servlet. So the last event that it sees was "READ". I think that this issue is not a serious one. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
