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

Tomek Rękawek edited comment on OAK-3743 at 12/16/15 8:33 AM:
--------------------------------------------------------------

I think that switching to the H2 fixed the issue. The build 
[627,jdk1.8.0_11|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=unittesting/627/]
 on the ubuntu-6 succedeed. When using Derby, all RDB builds on this machine 
were timing out.


was (Author: tomek.rekawek):
I think that switching to the H2 fixed the issue. The build 
[627|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=unittesting/627/]
 on the ubuntu-6 succedeed. When using Derby, all RDB builds on this machine 
were timing out.

> 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
>            Assignee: Thomas Mueller
>              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)

Reply via email to