Maybe we should put the qualified failure in the exclude list with a comment point to the
related JIRA issue. I know some projects do that :-)
Adrian Brock wrote:
On Thu, 2008-06-26 at 14:30 +0200, Sacha Labourey wrote:
> In case you usually don't look at the result of the AS testsuite, here
> is the list of the 39 remaining failing tests:
Some of these already have fixes they've just not been committed.
> * org.jboss.test.jmx.test.DeployXMBeanUnitTestCase.testSecuredJndiXMBean
> *
> org.jboss.test.jmx.test.DeployXMBeanUnitTestCase.testPersistentJndiXMBean
Anil has a fix for this (and probably some other tests that use
the legacy SecurityAssociation in the client?).
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138047
> *
> org.jboss.test.naming.test.NamingRestartUnitTestCase.testLookupLink
Brian has a fix for this here:
http://jira.jboss.com/jira/browse/JBNAME-3
> *
> org.jboss.test.jcaprops.test.JBossRaXmlOverrideUnitTestCase.testJBossRaXmlOverride
Vicky has an uncommitted fix for this as well:
http://jira.jboss.com/jira/browse/JBAS-3415
> * org.jboss.test.jmx.test.JMXConnectorUnitTestCase.testNotification
> *
> org.jboss.test.jmx.test.JMXConnectorUnitTestCase.testNotificationWithBadListener
>
There's a long discussion about this here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137781
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development