You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2017/08/23 21:02:00 UTC

[jira] [Resolved] (SLING-4996) FullTextIndexingTest needs very long (60 seconds) timeout for Oak

     [ https://issues.apache.org/jira/browse/SLING-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu resolved SLING-4996.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Launchpad Testing 9

> 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
>            Assignee: Robert Munteanu
>            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)