No, it will just mitigate the panic attack you had today.
In the metadata project, I see two test failues:
----------------------------------
Results :
Failed tests:
testSimpleProperties(org.jboss.test.metadata.ejb.JBossSessionBeanOverrideUnitTestCase)
testSimpleProperties(org.jboss.test.metadata.ejb.JBossMessageDrivenBeanOverrideUnitTestCase)
Tests run: 208, Failures: 2, Errors: 0, Skipped: 0
------------------------------------
Dimitris Andreadis wrote:
Sure, rolling back commits is my favorite pastime, those days.
Anil Saldhana wrote:
> Dimitris, roll back to the last beta version of MetaData (Beta16).
>
> Sacha Labourey wrote:
>> OK, I see. Still, here, we are speaking about +1162 failures, that
>> should be easy to detect just by starting any AS+app, no? ;)
>>
>> On 06/04/2008 02:15 PM, Dimitris Andreadis wrote:
>>> I suppose because it's hard for individual users to make a full
>>> local testsuite run before every commit. It takes 5-6 hours.
>>>
>>> I'd be happy if people would monitor subsequent hudson runs to see
>>> the effects of their commits.
>>>
>>> The AS5 testsuite is now more or less stable/predictable so it's
>>> easy to spot regression.
>>>
>>> Sacha Labourey wrote:
>>>> why aren't we able to catch those regression *before* we commit
>>>> them to SVN?
>>>>
>>>> On 06/04/2008 12:50 PM, Alexey Loubyansky wrote:
>>>>> Yes, it comes from metadata. The tests fail to deploy. Emanuel is
>>>>> going to look into it.
>>>>>
>>>>> Caused by: java.lang.IllegalArgumentException: Can't find
>>>>> interface null in
>>>>>
org.jboss.metadata.ejb.jboss.JBossSessionBeanMetaData@af9ed402{AuditSessionEJB}
>>>>>
>>>>> at
>>>>>
org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.determineResolvedJndiName(JBossEnterpriseBeanMetaData.java:702)
>>>>>
>>>>> at
>>>>>
org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.mapEjbs(MappedReferenceMetaDataResolverDeployer.java:332)
>>>>>
>>>>> at
>>>>>
org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.mapEndpoints(MappedReferenceMetaDataResolverDeployer.java:219)
>>>>>
>>>>> at
>>>>>
org.jboss.deployment.MappedReferenceMetaDataResolverDeployer.internalDeploy(MappedReferenceMetaDataResolverDeployer.java:140)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
>>>>>
>>>>>
>>>>>
>>>>> Dimitris Andreadis wrote:
>>>>>> I suspect this huge regression (+1162 failures) is related to the
>>>>>> recent jboss-metadata update:
>>>>>>
>>>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...