Hi Joachim:
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 frag
Hi,
> On Apr 1, 2014, at 11:11, 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 stag
I'm going to read up on Ian's Buildbot work and experiment with that in the
meantime. If other challenges come up I'm glad to dive in and help.
> On Apr 1, 2014, at 12:03, Simon Peyton Jones wrote:
>
> Indeed, there is no reason not to use Ian et al's Builder stuff. It's one of
> the options
Thank you Carter.
I think it's reasonable to incubate it on your Github profile for now until we
are certain it is fully working again. Either way works though :)
Best,
Alain
> On Apr 1, 2014, at 17:45, Carter Schonwald wrote:
>
> hey all, I just exported the igloo builder code from darcs to
I have trouble with this as it breaks expectations around directory structure
mirroring the module hierarchy.
I would be very confused reading the source code of a project that availed of
this feature as it would break my expectations of how to navigate to source
files based on their module hie
-1 for me. In case that was unclear.
On 25 April 2014 14:57, Alain O'Dea wrote:
> I have trouble with this as it breaks expectations around directory
> structure mirroring the module hierarchy.
>
> I would be very confused reading the source code of a project that availed
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/31/2014 12:28 PM, George Colpitts wrote:
> +1
>
> Stability is very important.
>
> Also, do we have an ETA for when we will have an improved
> infrastructure for automated builds and the associated tests. I
> think this would help a lot with st
