[JBoss-dev] Re: Remaining tasks for JBAS 4.0.5.CR1

[Dimitris Andreadis]

If the EJB3 team wants to improve the status of the ejb3-4.0-testsuite,
today is the last day to act.

We will tag 4.0.5.CR1 tomorrow and hand over to AlexP for building the
installer.

I'll create container tasks to track the improvement of the testsuite
runs for the other JVM combinations, for the next release.

> -----Original Message-----
> From: Ruel Loehr 
> Sent: Wednesday, August 30, 2006 5:53 PM
> To: JBoss.org development list; Dimitris Andreadis
> Cc: Ivelin Ivanov; Sacha Labourey
> Subject: RE: [JBoss-dev] Re: Remaining tasks for JBAS 4.0.5.CR1
> 
> So the sun 1.4 testsuite is passing:
> 
> http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuit
> e-sun-1.4/20060830062405/results/index.html
> 
> The only thing we are waiting on at this point is for the 
> ejb3 problems to addressed?
> 
> http://cruisecontrol.jboss.com/cc/artifacts/ejb3-4.0-testsuite
> /20060829220003/results/index.html
> 
> Ruel Loehr
> JBoss, a division of Red Hat
> QA
>  
> -----------------------------
> 512-342-7840 ext 2011
> Yahoo: ruelloehr
> Skype: ruelloehr
> AOL: dokoruel
> 
> -----Original Message-----
> From: jboss-development-bounces at lists.jboss.org 
> [mailto:jboss-development-bounces at lists.jboss.org] On Behalf 
> Of Scott M Stark
> Sent: Wednesday, August 30, 2006 9:46 AM
> To: Dimitris Andreadis
> Cc: Ivelin Ivanov; JBoss.org development list; Sacha Labourey
> Subject: [JBoss-dev] Re: Remaining tasks for JBAS 4.0.5.CR1
> 
> I agree with the testsuite strategy of addressing the other 
> vms for the final release.
> 
> Dimitris Andreadis wrote:
> > Hi,
> >
> > There are a couple of things left for the jbas 4.0.5.CR1 release.
> >
> > There are some harmless but annoying warnings that appear 
> upon server 
> > shutdown (see the bottom of this message). Three of them 
> are triggered 
> > by the embedded jbossws.beans in jbossws14.sar, but it seems to be 
> > caused by the MainDeployer / Bean deployer?
> > http://jira.jboss.com/jira/browse/JBAS-3471 (any ideas?)
> >
> > Apart from that, we have the testsuites to fix and a 
> decision to make.
> > We currently run Branch_4_0 under the following JVM 
> combinations with 
> > the corresponding results.
> >
> > 1) Sun JVM 1.4 --> 6 failures
> > 2) Sun JVM 5   --> 10 failures
> > 3) Jrockit 1.4 --> 58 failures
> > 4) Jrockit 5   --> 63 failures
> >
> > Traditionally we only care about the Sun JVM 1.4 test runs. 
> Does this 
> > still hold true, or if not, how far to go with the other JVM 
> > combinations? Looking into the failures, I don't think we can reach 
> > 100% on all of them within the limits of this CR release, so I'd 
> > suggest we target 100% on (1) and schedule JIRA tasks for 
> addressing 
> > the other failures in future releases.
> >
> > Also note, that many of the failures are transient.
> >
> > Finally, somebody needs to look into the 28 ejb3 testsuite failures.
> >
> > Please take a look at the remaining tasks, or even if not assigned 
> > have a go with the remanining testsuite failures 
> > 
> http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=
> > hi 
> > 
> de&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10030&fix
> > fo
> > r=12310576
> >
> > Thanks
> > /Dimitris
> >
> >
> >   
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.11.7/433 - Release 
> Date: 8/30/2006
>  
> 
> -- 
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.11.7/433 - Release 
> Date: 8/30/2006
>  
>