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 Mon, 04 Aug 2014 08:36:13 GMT

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

Michael Dürig commented on OAK-1855:

I like the {{FixturesHelper}} approach and the separation of integration and unit tests. I
also think it is a good idea to only run against a default fixture (e.g. segment) for local
builds and making this overrideable through the {{ns-fixtures}} property. What confuses me
is the proliferation of profiles. Do we need {{ITSegmentMK}} and {{ITDocumentALL}}? Both are
mostly copies of the {{integrationTesting}} profile. Can't we specify that property override
directly to Travis? Also I'm not clear about the {{pedantic}} profile. What tests on what
fixtures does this one run? 

> 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
>            Assignee: Davide Giannella
>         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