[Agda-dev] Re: Travis: statically linked executables for master

[gallais]

Hi,

Thinking about this a bit more: one alternative strategy would be
to have a build-binary branch which the travis job run on master
pushes to if the build and tests are successful and does nothing
but creating the binary.

The test suite takes about 8 minutes to run so that'd give us a
bit of breathing room.

Cheers,

On 06/01/15 19:03, gallais wrote:
> Hi all, Happy New Year!
>
> Before merging the work I've done on using travis-ci to build
> documentation for the standard library (which we're discussing
> here [1]), I figured it'd be nice to have a more reliable
> process: rather than fetching the master branch no matter whether
> it compiles and passes the test suite or not, I'd rather grab
> a working executable.
>
> So I have been working on getting travis to produce a statically
> linked Agda executable on my build-binary branch [2]. I have
> now reached the point where it "just works" [3, 4].
>
> However the builds [3] seem to take longer (with the ghc-7.8.3
> one being awfully close to time-out) so I figured I'd ask here
> what the next step is:
> - do you know of tricks to speed-up the build?
> - do we want to use this .travis.yml on master?
>
> Cheers,
>
> -- 
> gallais
>
> [1] https://github.com/agda/agda-stdlib/issues/45
> [2] https://github.com/gallais/agda/tree/build-binary
> [3] https://travis-ci.org/gallais/agda/builds/46099712
> [4] 
> https://www.dropbox.com/sh/yn8pr2jorbzsy2g/AABc445eZQIwnXqEuPody0pga?dl=0