Hi Developers / Committers, FYI, it seems that some of our DSpace Pull Requests are encountering random build failures via Travis CI (which we use to validate that a PR builds properly). These build failures seem to be a result of Travis CI randomly "killing" the build script. When it occurs, you'll see something like this at the end of the logs on Travis-ci.org:
/home/travis/build.sh: line 93: 20128 Killed I haven't been able to track down exactly why this is happening. But here's a little info from Travis CI itself: http://docs.travis-ci.com/user/common-build-problems/#My-build-script-is-killed-without-any-error I suspect we *may* be hitting up against Travis CI's 3GB memory limit during unit testing / building, similar to this issue report: https://github.com/travis-ci/travis-ci/issues/2109 I have determined that often times, simply retrying the build will work (sometimes a few times). You can tell Travis CI to retry the build just by logging into Travis CI and clicking the "Restart Build" button in the upper right (of the failed build). But, we may need to be in search of a longer term solution. - Tim -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
