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

ASF GitHub Bot commented on THRIFT-3303:
----------------------------------------

GitHub user nsuke opened a pull request:

    https://github.com/apache/thrift/pull/592

    THRIFT-3303 Disable concurrent cabal jobs on Travis to avoid GHC crush

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nsuke/thrift THRIFT-3303

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/thrift/pull/592.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #592
    
----
commit 9a03dbb86ae5ee075d471f89c0f0b723128c2398
Author: Nobuaki Sukegawa <nsu...@gmail.com>
Date:   2015-08-23T09:35:15Z

    THRIFT-3303 Disable concurrent cabal jobs on Travis to avoid GHC crush

----


> Disable concurrent cabal jobs on Travis to avoid GHC crush
> ----------------------------------------------------------
>
>                 Key: THRIFT-3303
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3303
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Build Process
>            Reporter: Nobuaki Sukegawa
>            Assignee: Nobuaki Sukegawa
>
> Recently more than half of Travis builds are failing because of GHC crush 
> seemingly due to out of memory.
> Several examples of such failures:
> https://travis-ci.org/apache/thrift/jobs/75674316
> https://travis-ci.org/apache/thrift/jobs/75674316
> https://travis-ci.org/apache/thrift/jobs/74296672
> https://travis-ci.org/apache/thrift/jobs/74296672
> https://travis-ci.org/apache/thrift/jobs/73955088
> The patch forces number of cabal install jobs to 1 so that it does not 
> consume too much resource.
> I've run several Travis builds with this setting and it's quite stable now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to