[
https://issues.apache.org/jira/browse/TAMAYA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger resolved TAMAYA-324.
--------------------------------------
Resolution: Fixed
Fix Version/s: 0.4-incubating
Applied patch via
{code:java}
patch -p1 < ....patch{code}
let's see if tests do not fail on ASF Jenkins.
Local runs are okay on similar LTS ubuntu systems.
William, thanks for your patch and help!
> CDI-Test failures in extensions modules on certain environments
> ---------------------------------------------------------------
>
> Key: TAMAYA-324
> URL: https://issues.apache.org/jira/browse/TAMAYA-324
> Project: Tamaya
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.4-incubating
> Reporter: Philipp Ottlinger
> Assignee: Philipp Ottlinger
> Priority: Major
> Fix For: 0.4-incubating
>
> Attachments: TAMAYA-324.patch
>
>
> Certain ASF nodes with older Ubuntu LTS versions show test failures in
> CDI-Tests:
> {code:java}
> Tests in error:
> CDIAwareServiceContextTest.getServiceReturnsInstanceWithHighestPriority:57
> » IllegalState
> CDIAwareServiceContextTest.getServiceReturnsNonCachedInstanceAtFirstCall:32
> » IllegalState
>
> CDIAwareServiceContextTest.getServiceReturnsNullIfThereAreNoRegisteredSPIInstancesAvailable:50
> » IllegalState
> CDIAwareServiceContextTest.getServiceReturnsOnSecondCallCachedInstance:40 »
> IllegalState
> {code}
>
> h2. Williams commits:
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
