Hi there.

I've been looking into the recent test failures on the extensions builds [1] 
and I think I've got a pretty good handle on it.   Check out 
https://github.com/peculater/incubator-tamaya-extensions/compare/NOJIRA-test-idempotency?w=1
 for what I think is happening there.  There are two fixes described in that 
commit:

First, the CDIAwareServiceContextTest now uses the same Arquillian
backing as various other successful tests.

Second, the ConfiguredVetoExtensionTest is now more idempotent with respect
to the ConfigurationProvider.  Previously, it would leave the shared
ConfigurationProvider pointing at the mocked ConfigurationContext, which
caused other tests (specifically ConfiguredBTest) which rely on a valid
ConfigurationContext to fail.

After making these changes, the tests run successfully for me consistently.  I 
don't see a jira ticket for the errors, but am happy to update my commit 
messages if I missed one.  I also probably need to sign whatever contributor 
forms are relevant for this project.

Thoughts?
--William Lieurance 


1.  Example from yesterday: 
https://builds.apache.org/view/S-Z/view/Tamaya/job/Tamaya-Extensions-Master/1317/org.apache.tamaya.ext$tamaya-cdi/#showFailuresLink

Reply via email to