[
https://issues.apache.org/jira/browse/SLING-8246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996979#comment-16996979
]
Scott Yuan commented on SLING-8246:
-----------------------------------
Hi Robert, having a exclusion list for problematic OSGi bundles would work
perfectly for my need. If there hasn't been a work done for it yet, I can
provide a pull request to give it a try.
-Scott Yuan
> Server side test hang with repeat "Waiting for the following bundles to
> start:..." in log
> -----------------------------------------------------------------------------------------
>
> Key: SLING-8246
> URL: https://issues.apache.org/jira/browse/SLING-8246
> Project: Sling
> Issue Type: Improvement
> Components: Apache Sling Testing Clients, JUnit Core
> Affects Versions: JUnit Core 1.0.20, JUnit Core 1.0.22, JUnit Core 1.0.23,
> JUnit Core 1.0.24, JUnit Core 1.0.26
> Environment: OS: Windows, Linux
> Java: Java 1.8
> Reporter: Scott Yuan
> Priority: Major
> Attachments: patch.diff
>
> Original Estimate: 0.5h
> Time Spent: 10m
> Remaining Estimate: 20m
>
> +SLING-6334 - Server-Side Tests: Wait until all bundles are started be…+ had
> been a great feature for ensuring accurate test results. Thanks for having
> this feature available.
> I recently found that if there is a bundle failed to start; SLING-6334
> doesn't timeout after DEFAULT_SYSTEM_STARTUP_INACTIVITY_TIMEOUT_SECONDS but
> waits infinitely with repeating log message
> {noformat}
> 26.01.2019 13:58:14.562 *INFO* [qtp980475582-2859]
> org.apache.sling.junit.impl.TestsManagerImpl Waiting for the following
> bundles to start: [adobe-aemfd-signatures [777],
> com.ags.forms.commom.ags_forms_common [854]]
> {noformat}
> In my case, we needed the server side tests continue to work while the bundle
> starting problem being addressed in parallel. With some studies to the source
> code, the issue can be fixed by a single liner change in the attached .diff
> file.
> Hopefully, the problem can be addressed in the upcoming 1.0.27 release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
