[
https://issues.apache.org/jira/browse/OAK-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052701#comment-15052701
]
Tomek Rękawek commented on OAK-3743:
------------------------------------
Going further, all "slow" tests are children of the {{AbstractRepositoryTest}},
which takes the {{DocumentNodeStore}} and creates a JCR repository. I suppose
that the {{Jcr()}} introduces the performance problems.
Another fact - the {{ReferenceBinaryIT}} which also creates a JCR repository,
remains fast. The only difference in the JCR instantiation between
{{AbstractRepositoryTest}} and {{ReferenceBinaryIT}} is that in the former
there are two extra settings added:
{code}
QueryEngineSettings qs = new QueryEngineSettings();
qs.setFullTextComparisonWithoutIndex(true);
return jcr.withAsyncIndexing().with(qs);
{code}
So, I suppose that the cause of the problem lies here.
> Build time out after 90 mins on Jenkins
> ---------------------------------------
>
> Key: OAK-3743
> URL: https://issues.apache.org/jira/browse/OAK-3743
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: rdbmk
> Environment: Jenkins, Ubuntu:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
> Reporter: Michael Dürig
> Labels: CI, Jenkins
> Fix For: 1.4
>
> Attachments: OAK-3743-parallelized.patch
>
>
> Every 2nd build or so is aborted after a time out (90 mins):
> {noformat}
> Build timed out (after 90 minutes). Marking the build as aborted.
> Build was aborted
> [FINDBUGS] Skipping publisher since build result is ABORTED
> Recording test results
> Finished: ABORTED
> {noformat}
> See e.g.
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/585/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=unittesting/console
> Interestingly when successful, the build takes about 30mins, so way below the
> 90 min. timeout.
> Also seen at builds 587, 590, 591, 593, 595, 597, 598, 604, 608, 609, 610
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
