Travis builds failing

[Austin Seipp]

I don't think there's any built-in way to do that in the current
testsuite infrastructure, other than setting THREADS=1, which, if it
isn't set already, would probably push us back over the Travis build
limit.

I wonder if we could just ask if they'd increase the limit for our project...

On Mon, Jun 1, 2015 at 2:23 PM, Alan & Kim Zimmerman
<alan.zimm at gmail.com> wrote:
> Is is possible to limit the number of concurrent tests? Instead of running
> on all available cores.
>
> On Mon, Jun 1, 2015 at 9:16 PM, Austin Seipp <austin at well-typed.com> wrote:
>>
>> Looks like:
>>
>> collect2: ld terminated with signal 9 [Killed]
>>
>> which I'd say with fair certainty means that the jobs failed because
>> the linker ran out of memory on Travis, and the OOM killed it. So,
>> that's a thing now.
>>
>> Perhaps for travis builds, we could disable SplitObjs by default to
>> relieve the memory pressure? I'm not sure if it's on during Travis's
>> builds, but it's a thought.
>>
>> On Mon, Jun 1, 2015 at 1:30 PM, Alan & Kim Zimmerman
>> <alan.zimm at gmail.com> wrote:
>> > I suspect this is different, I am building a local master now, at
>> > current
>> > HEAD a27fb46ff1ea46a45e0084c3db92a24475e3bab5 to see what I find.
>> >
>> > Alan
>> >
>> > On Mon, Jun 1, 2015 at 8:22 PM, Joachim Breitner
>> > <mail at joachim-breitner.de>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >>
>> >> Am Montag, den 01.06.2015, 13:44 +0200 schrieb Alan & Kim Zimmerman:
>> >> > On Mon, Jun 1, 2015 at 1:25 PM, Joachim Breitner
>> >> > <mail at joachim-breitner.de> wrote:
>> >> > yay, travis is green again. Thanks to Alan for fixing this.
>> >>
>> >> > With a lot of help from @thomie ..
>> >>
>> >>
>> >> hmm, looks like it is not fixed after all:
>> >>
>> >> Unexpected failures:
>> >>    ghc-api                       T6145 [bad exit code] (normal)
>> >>    ghc-api                       T8628 [bad exit code] (normal)
>> >>    ghc-api                       T8639_api [bad exit code] (normal)
>> >>    ghc-api/annotations           T10278 [bad exit code] (normal)
>> >>    ghc-api/annotations           T10313 [bad exit code] (normal)
>> >>    ghc-api/annotations           T10354 [bad exit code] (normal)
>> >>    ghc-api/annotations           T10396 [bad exit code] (normal)
>> >>    ghc-api/annotations           T10399 [bad exit code] (normal)
>> >>    ghc-api/annotations           boolFormula [bad exit code] (normal)
>> >>    ghc-api/annotations-literals  parsed [bad exit code] (normal)
>> >>
>> >>
>> >> https://s3.amazonaws.com/archive.travis-ci.org/jobs/64945879/log.txt
>> >>
>> >> Greetings,
>> >> Joachim
>> >> --
>> >> Joachim “nomeata” Breitner
>> >>   mail at joachim-breitner.de • http://www.joachim-breitner.de/
>> >>   Jabber: nomeata at joachim-breitner.de  • GPG-Key: 0xF0FBF51F
>> >>   Debian Developer: nomeata at debian.org
>> >>
>> >> _______________________________________________
>> >> ghc-devs mailing list
>> >> ghc-devs at haskell.org
>> >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>> >>
>> >
>> >
>> > _______________________________________________
>> > ghc-devs mailing list
>> > ghc-devs at haskell.org
>> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Austin Seipp, Haskell Consultant
>> Well-Typed LLP, http://www.well-typed.com/
>
>



-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/