[weld-dev] Tests failures

[David Allen]

I have had the following failures on the TCK running out of container
for almost the last two months now:

Failed tests: 

testDecoratorInvokesDelegateMethodOutsideOfBusinessMethodInterception(org.jboss.jsr299.tck.tests.decorators.invocation.DecoratorInvocationTest)

testAmbiguousELNamesResolved(org.jboss.jsr299.tck.tests.lookup.byname.ResolutionByNameTest)

testFieldNameUsedAsBeanName(org.jboss.jsr299.tck.tests.lookup.byname.ResolutionByNameTest)

testNewBean(org.jboss.jsr299.tck.tests.lookup.dynamic.DynamicLookupTest)

I have not investigated any of these as of yet.  They were already there
before I started changing anything in Weld, so I believe they are
independent of proxies or other memory saving techniques.

- David

Am Freitag, den 21.05.2010, 22:57 +0100 schrieb Pete Muir:
> All
> 
> I've worked through the incontainer test failures we were seeing with Weld, and I am now down to these locally:
> 
>   testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest)
>   testPassivationOfPersistenceContext(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest)
>   testPassivationOfPersistenceUnit(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest)
> 
> All of which are related to serialization of proxies. David is going to take a look on Sunday at these.
> 
> If you see other failures locally, please investigate or discuss :-)
> 
> Pete
> 
> 
> _______________________________________________
> weld-dev mailing list
> weld-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev