[jboss-dev] Re: Community
Brian Stansberry
brian.stansberry at redhat.com
Fri Jul 13 13:10:51 EDT 2007
Good news, bad news.
Good news:
A lot of the clustering tests get executed multiple times with different
configs. Accounting for that, the # of clustering failures is 17 and #
of errors is 7.
Bad news:
The # of clustering failures is 17 and # of errors is 7.
I've been knocking off failures for a few weeks now and will keep at it
until they're gone.
Sacha Labourey wrote:
> OK, great, thanks Scott.
>
> Now, project leads, if your project is mentioned below, you know what's
> on your plate. We want 0 problem in this testsuite, otherwise, we send
> you "the cleaner" aka "Build Burke", and he will take care of your project.
>
> Onto 5.0!!!!!
>
>
> On 07/13/2007 06:06 PM, Rajesh Rajasekaran wrote:
>> Now we have the testsuite running to completion with Scott’s fixes
>> yesterday.
>>
>> http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-sun-1.5/20070712214357/results/index.html
>>
>>
>>
>>
>> Summary:
>>
>> **Tests Failures Errors Success rate**
>>
>> 3302 167 308 85.61%
>>
>>
>>
>> Some of the broad categories to start looking at:
>>
>>
>>
>> Clustering: 110 failures
>>
>>
>>
>> JBoss Messaging: 49 failures
>>
>>
>>
>> Jboss web: 34 failures
>>
>>
>>
>> Deployers: 25 failures
>>
>>
>>
>> JBoss MX: 27 failures
>>
>>
>>
>> Classloader: 16 failures
>>
>>
>>
>> Jacc: 14 failures
>>
>>
>>
>> Profileservice: 13 failures
>>
>>
>>
>> Security: 12 failures
>>
>>
>>
>> Jca: 12 failures
>>
>>
>>
>> Jaxr: 9 failures
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> *From:* thecore-bounces at redhat.com [mailto:thecore-bounces at redhat.com]
>> *On Behalf Of *Andrig T Miller
>> *Sent:* Thursday, July 12, 2007 4:39 PM
>> *To:* Sacha Labourey
>> *Cc:* rcampbel at redhat.com; The Core; bill at jboss.org
>> *Subject:* Re: Community
>>
>>
>>
>> If you guys want, I can open the JIRA's for the failing tests, since I
>> poor over the build logs for the e-mail I have sent out the last two
>> Monday's anyway. The only thing I will need some help with is how I
>> determine who to assign it too. Is there something in the build log I
>> can key off of for specific tests?
>>
>> Andy
>>
>> On Tue, 2007-07-10 at 16:27 +0200, Sacha Labourey wrote:
>>
>>
>>
>> Whatever is the solution, who is responsible for this? who is stepping
>> up to get back to an healthy point, we are not going to go anywhere with
>> 5.0 unless this is fixed, now.
>>
>>
>>
>
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry at redhat.com
More information about the jboss-development
mailing list