[
https://issues.apache.org/jira/browse/SLING-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912443#comment-17912443
]
Stefan Seifert commented on SLING-12415:
----------------------------------------
[~cnagel] with which actual increased timeout values did you have an success in
your environment?
we do not want to set it too high to very large value to not have unit tests
wait too long if there is really a persistent error with the resource resolver.
> Intermittent build failures on Sling Test envs -
> ResourceResolverFactoryActivator 250 ms
> ----------------------------------------------------------------------------------------
>
> Key: SLING-12415
> URL: https://issues.apache.org/jira/browse/SLING-12415
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Reporter: Niek Raaijmakers
> Priority: Major
>
> SLING-12090 introduced some cases where unit tests failed intermittently:
> We see:
>
> {code:java}
> 09:01:47,710 [ThreadedStreamConsumer] [ERROR] Tests run: 2, Failures: 0,
> Errors: 1, Skipped: 0, Time elapsed: 2.016 s <<< FAILURE! - in
> com.x.y.z.MoreLandingPagesServletTest 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}
>
> Perhaps we could increase the timeout?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
