Am 27.11.2017 um 22:19 schrieb Apache Jenkins Server:
> See
> <https://builds.apache.org/job/Tamaya-Extensions-Master-with-Coverage/241/display/redirect>
>
The CDI failures I experience locally are back on CI as well:
Testergebnis (11 fehlgeschlagene Tests / +7)
org.apache.tamaya.cdi.ConfigurationProducerTest.optionalIntegerFieldIsSet
org.apache.tamaya.cdi.ConfigurationProducerTest.actualPropertyValues
org.apache.tamaya.cdi.ConfigurationProducerTest.providerIntegerFieldIsSet
org.apache.tamaya.cdi.ConfigurationProducerTest.optionalStringFieldIsSet
org.apache.tamaya.cdi.ConfigurationProducerTest.defaultValues
org.apache.tamaya.cdi.ConfigurationProducerTest.providerStringFieldIsSet
org.apache.tamaya.cdi.ConfiguredBTest.test_Configuration_is_injected_correctly
org.apache.tamaya.cdi.CDIAwareServiceContextTest.getServiceReturnsNullIfThereAreNoRegisteredSPIInstancesAvailable
org.apache.tamaya.cdi.CDIAwareServiceContextTest.getServiceReturnsInstanceWithHighestPriority
org.apache.tamaya.cdi.CDIAwareServiceContextTest.getServiceReturnsOnSecondCallCachedInstance
org.apache.tamaya.cdi.CDIAwareServiceContextTest.getServiceReturnsNonCachedInstanceAtFirstCall
Any ideas?
Should we split all of the tests in case of side effects?
Phil
