Buildbots
Alain O'Dea
alain.odea at gmail.com
Tue Apr 1 11:22:16 UTC 2014
Hi,
> On Apr 1, 2014, at 11:11, Joachim Breitner <mail at joachim-breitner.de> 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)
Good points.
> Hence: Travis is _not_ going to be a solution for us; we will want our
> own infrastructure.
I'm happy to assist with getting whatever system fits the bill working. It seems like Buildbot should.
Where can we get infrastructure on multiple architectures easily? I imagine we may need to
mix and match.
> Greetings,
> Joachim
>
> --
> Joachim “nomeata” Breitner
> mail at joachim-breitner.de • http://www.joachim-breitner.de/
> Jabber: nomeata at joachim-breitner.de • GPG-Key: 0x4743206C
> Debian Developer: nomeata at debian.org
More information about the ghc-devs
mailing list