You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/01/20 20:34:00 UTC
[jira] [Commented] (TAMAYA-324) CDI-Test failures in extensions
modules on certain environments
[ https://issues.apache.org/jira/browse/TAMAYA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333312#comment-16333312 ]
ASF subversion and git services commented on TAMAYA-324:
--------------------------------------------------------
Commit 8f657bb92d6c656b0724a83d875063ad2c011e60 in incubator-tamaya-extensions's branch refs/heads/master from Hugo Hirsch
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=8f657bb ]
TAMAYA-324: Fixes for test failures provided by William Lieurance
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.
> 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
> 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)