[
https://issues.apache.org/jira/browse/SLING-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701899#comment-13701899
]
Stefan Egli commented on SLING-2945:
------------------------------------
[~rombert], excellent. That patch looks good. I might add some more asserts to
the Condition there to check not only the count but if the correct instances
are visible. But I can apply that after patch.
Re the exception: jup, I should probably have done some more safety-checks
there - but the catch is fine for now.
> ClusterLoadTest failures
> ------------------------
>
> Key: SLING-2945
> URL: https://issues.apache.org/jira/browse/SLING-2945
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Robert Munteanu
> Assignee: Stefan Egli
> Attachments: SLING-2945-retry-loop.patch
>
>
> This test has failed recently on Jenkins at [1], with the message:
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.sling.discovery.impl.cluster.ClusterLoadTest
> Build timed out (after 150 minutes). Marking the build as failed.
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> To debug infra issues, I've also set up a Travis CI build at [2] . This test
> also fails there, but the error message is clearer: Caused by:
> javax.jcr.PathNotFoundException: /var/discovery/impl . The full build log is
> at [3].
> I also have errors when repeatedly running the test locally, so it's not just
> CI flakiness.
> [1] :
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/1715/console
> [2]: http://travis-ci.org/rombert/sling/
> [3]: https://s3.amazonaws.com/archive.travis-ci.org/jobs/8746894/log.txt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
