[
https://issues.apache.org/jira/browse/SLING-12090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877043#comment-17877043
]
Niek Raaijmakers commented on SLING-12090:
------------------------------------------
[~sseifert]
{code:java}
09:01:47,710 [ThreadedStreamConsumer] [ERROR] Tests run: 2, Failures: 0,
Errors: 1, Skipped: 0, Time elapsed: 2.016 s <<< FAILURE! - in <removed
customer package to protect the innocent> 09:01:47,710 [ThreadedStreamConsumer]
[ERROR] testDoGetLandingPagesServlet Time elapsed: 0.012 s <<< ERROR!
java.lang.RuntimeException: Unable to initialize JCR_MOCK resource resolver
factory: ResourceResolverFactoryActivator did not register a
ResourceResolverFactory after 250ms. Caused by:
java.lang.IllegalStateException: ResourceResolverFactoryActivator did not
register a ResourceResolverFactory after 250ms.{code}
A customer of us is getting this in their build step intermittently.
Can we increase the timeout somewhat perhaps?
> sling-mock: Make compatible with ResourceResolver 1.11.0
> --------------------------------------------------------
>
> Key: SLING-12090
> URL: https://issues.apache.org/jira/browse/SLING-12090
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing Sling Mock 3.4.12
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing Sling Mock 3.4.14
>
>
> SLING-12019 introduced a change in ResourceResolverFactoryActivator which
> changes the registration of ResourceResolverFactory services into an
> asynchronous process - which breaks most of the sling-mock based unit tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)