On Tue, Apr 1, 2014 at 1:11 PM, Joachim Breitner wrote:
Hi,
Am Dienstag, den 01.04.2014, 11:08 +0000 schrieb Alain O'Dea:
From what I understand Travis CI limits running time for each build. We may be able to create binaries of stage1 and/or stage2 in one build and test them in another. We could also fan out the test process using a Build Matrix to let GHC's full suite fit into the time limit as fragments. That would require some changes to the testsuite or some lengthy build scripts for each segment that explicitly run many "make TEST=sometest" commands.
The main problem with Travis is that it only tests on one architecture. There are more (e.g. very undetailed reporting compared to a buildbot waterfall/grid)
Hence: Travis is _not_ going to be a solution for us; we will want our own infrastructure.
I do agree, but if anybody wants to look more closely into using Travis-CI, I suggest to also consider drone.io. It appears to fix some of the shortcomings and annoyances of Travis-CI.