jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-1855) Travis builds time out
Date Tue, 29 Jul 2014 15:15:39 GMT

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

Michael Dürig commented on OAK-1855:

We could also "stripe" the individual fixtures: Just running {{mvn clean install}} it would
run all unit tests against the segment node store. Running against different/additional fixtures
could be achieved through environment variables/command line arguments. This way people working
on the code could just run the tests against their favourite back end. On Travis we could
schedule separate jobs for each of the fixtures. 

Only if this is not sufficient would I go on and partition the current tests into separate

> Travis builds time out
> ----------------------
>                 Key: OAK-1855
>                 URL: https://issues.apache.org/jira/browse/OAK-1855
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Marcel Reutegger
>         Attachments: OAK-1855-ut-times.txt
> Recently quite many travis builds failed because they hit the 50 minutes time limit.
> Possible solutions that come to my mind:
> - reduce the time our tests take
> - split up the build with multiple profiles

This message was sent by Atlassian JIRA

View raw message