[
https://issues.apache.org/jira/browse/SLING-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139098#comment-16139098
]
Robert Munteanu commented on SLING-4996:
----------------------------------------
After restoring the test ( SLING-7081 ) the test finished in 10-15 seconds for
3 passes, so that's 3-5 seconds per individual test.
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.653 sec - in
org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.051 sec - in
org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest
In [r1805959|https://svn.apache.org/r1805959] I've set the timeout to 15
seconds per test, should be more than enough.
> FullTextIndexingTest needs very long (60 seconds) timeout for Oak
> -----------------------------------------------------------------
>
> Key: SLING-4996
> URL: https://issues.apache.org/jira/browse/SLING-4996
> Project: Sling
> Issue Type: Bug
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Labels: sling-it
> Fix For: Launchpad Testing 9
>
>
> I had to increase the timeout to 60 seconds in the
> {{launchpad/integration-tests/.../FullTextIndexingTest}} to make it pass
> reliably with Oak on Jenkins.
> I suspect the Oak indexes are not always ready when the test runs: the error
> log shows "org.apache.jackrabbit.oak.plugins.index.IndexUpdate Indexing
> report" messages after the test runs, which I suppose signals the end of an
> indexing task.
> We should find out how to take this into account in the tests, either wait
> for all required indexes to be ready before starting our tests, or having a
> way to find out whether a specific set of indexes is ready before starting a
> specific test.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
