Return-Path: X-Original-To: apmail-tomcat-dev-archive@www.apache.org Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AEB7110914 for ; Wed, 2 Oct 2013 17:28:20 +0000 (UTC) Received: (qmail 69098 invoked by uid 500); 2 Oct 2013 17:28:18 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 69020 invoked by uid 500); 2 Oct 2013 17:28:17 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 69011 invoked by uid 99); 2 Oct 2013 17:28:16 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 17:28:16 +0000 Received: from localhost (HELO [192.168.23.9]) (127.0.0.1) (smtp-auth username markt, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 17:28:16 +0000 Message-ID: <524C57AA.4020501@apache.org> Date: Wed, 02 Oct 2013 18:28:10 +0100 From: Mark Thomas User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: 8.0.x / 7.0.x progress References: <524B16DC.50506@apache.org> In-Reply-To: <524B16DC.50506@apache.org> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 01/10/2013 19:39, Mark Thomas wrote: > 8.0.x trunk appears to be stable (i.e. no longer crashes) So far no-one has come forward with results to contradict this and folks that reported issues with RC3 have not been able to repeat them. The additional issues reported with the snake example have been resolved. Currently, the 8.0.x unit tests pass (with tomcat native built from 1.1.x) for BIO, NIO and APR/native. > but the > FormAuthenticator unit tests are very slow (24 minutes). This needs to > be resolved. This has been resolved. > I will port the latest APR changes to 7.0.x shortly. Also done. > A build of the latest 1.1.x tomcat-native code is required to achieve > that stability. The implication is that a 1.1.29 release will be > required before the next 7.0.x release. I'm now certain that a tomcat native 1.1.29 release will be required before we can roll the next 7.0.x release. > The unit tests have identified a rare failure mode in JULI during > context stop: > http://ci.apache.org/projects/tomcat/tomcat7/logs/1527504/TEST-org.apache.catalina.websocket.TestWebSocket.NIO.txt This does not appear to be connector related so it is very unlikely that any tomcat native changes would be required to fix this. > The fairly frequent (5%-10%) failure rate of TestCoyoteOutputStream > still needs to be addressed. This appears to impact all connectors so at this point it is unlikely a tomcat native change would be required. I think we are at a point where it makes sense to start a tomcat native 1.1.29 release. Mladen? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org