sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-4996) FullTextIndexingTest needs very long (60 seconds) timeout for Oak
Date Wed, 23 Aug 2017 19:56:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138972#comment-16138972
] 

Robert Munteanu commented on SLING-4996:
----------------------------------------

Note that the test was removed in [r1797403|https://svn.apache.org/r1797403] for SLING-6928,
presumably as it was using the servlets.compat bundle to verifying the test results. However,
this should be restored.

> 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
>
> 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)

Mime
View raw message