[
https://issues.apache.org/jira/browse/SLING-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877601#comment-17877601
]
Stefan Seifert commented on SLING-12415:
----------------------------------------
do you have a unit test case or test project to reproduce the failure? do you
get this error permanently and reproducible, or only sometimes from time to
time?
do you get any other errors in the log file that might be related?
it would also be intersting to see the actual versions of all other libraries
in the (test)classpath, esp. the sling module ones.
not sure if it really helps to increase the timeout. it's not unlikely that
there is a problem that is not cured by this. you could verify this on your
side by testing it with a patched version of sling-mock with a higher timeout.
> 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)
