[
https://issues.apache.org/jira/browse/SLING-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060901#comment-17060901
]
Bertrand Delacretaz commented on SLING-9200:
--------------------------------------------
Thank you very much for your contribution, I have merged your PR and made minor
changes in [commit
7e7b214|https://github.com/apache/sling-org-apache-sling-junit-core/commit/7e7b214].
I have changed the "global timeout" name to "system startup timeout" as there's
no non-global timeouts left IIUC, so the system property to set that is now
{{sling.junit.core.SystemStartupTimeoutSeconds}}
I hope this works for you, please cross-check and if ok I think we can mark
this fixed.
> ServerSide test hang due to non activated bundles
> -------------------------------------------------
>
> Key: SLING-9200
> URL: https://issues.apache.org/jira/browse/SLING-9200
> Project: Sling
> Issue Type: Bug
> Components: JUnit Core
> Affects Versions: JUnit Core 1.0.26
> Reporter: Thierry Ygé
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Currently we observe that on AEM instance using API regions validation, that
> if some bundles are not started due to any outside reasons, the ServerSide
> test execution will go in a infinite waitForSystemStartup loop.
> Apparently reading at the code it would eventually expected a timeout , but
> the way the while condition loop is written it never get out. It actually
> miss some "global" timeout, so that it would allow to exit the loop and
> output the warning message that some bundles are not available, and it would
> still then execute the tests.
> cc [~bdelacretaz]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
