[weld-dev] Current WELD trunk Incontainer testing status

[Pete Muir]

A more recent run - http://hudson.jboss.org/hudson/job/Weld-trunk-incontainer-jboss-6.0.x/85/ - is now passing everything, so I think this was a transient problem caused by some missing update to JBoss AS probably.

Martin, next week lets ensure we have the dependency chain for running this job correct :-)

On 18 Feb 2010, at 09:32, Martin Gencur wrote:

> There are results from yesterday (2009-02-17) on Linux machine in
> Hudson:
> 
> 
> ---------Weld Core Tests-----------
> 
> Tests run: 231, Failures: 6, Errors: 0, Skipped: 0, Time elapsed:
> 429.714 sec <<< FAILURE!
> 
> Results :
> 
> Failed tests: 
>  testAlternativesOnProducers(org.jboss.weld.tests.alternatives.AlternativesTest)
>  testDetectsJsf12Version(org.jboss.weld.tests.jsf.JsfApiAbstractionTest)
>  testLoadsJsf12Classes(org.jboss.weld.tests.jsf.JsfApiAbstractionTest)
>  testLoadsJsf20Classes(org.jboss.weld.tests.jsf.JsfApiAbstractionTest)
>  testGetNamedBeanWithBinding(org.jboss.weld.tests.resolution.named.NamedBeanTest)
>  testNamedInjectedFieldUsesFieldName(org.jboss.weld.tests.resolution.named.NamedBeanTest)
> 
> 
> 
> --------CDI TCK runner for Weld---------
> 
> Tests run: 791, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1,490.474 sec <<< FAILURE!
> 
> Results :
> 
> Failed tests: 
>  testApplicationScopeActiveDuringCallToEjbTimeoutMethod(org.jboss.jsr299.tck.tests.context.application.ejb.EJBApplicationContextTest)
>  testSingletonWithConversationScopeFails(org.jboss.jsr299.tck.tests.implementation.enterprise.broken.singletonWithConversationScope.SingletonWithConversationScopeTest)
> 
> 
> All the other tests passed.
> 
> _______________________________________________
> weld-dev mailing list
> weld-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev