Travis builds failing

Alan & Kim Zimmerman alan.zimm at
Sat May 30 10:00:52 UTC 2015

Your mail seems to indicate that the processes were sent a SIGKILL during
the link phase.

To my knowledge this can happen in two ways: from the test runner for a
timeout or from the kernel for an out of memory condition.

I suspect the timeout is not the culprit.

Is there any way to check for out of memory kills on the travis box?

Or is there another way it can be killed?


On Fri, May 29, 2015 at 10:42 PM, Joachim Breitner <mail at
> wrote:

> Hi,
> Am Donnerstag, den 28.05.2015, 17:46 -0700 schrieb Edward Z. Yang:
> > To whoever manages our Travis setup
> that would be me.
> > We seem to be failing because our build takes longer than 50min.
> that happens occasionally, yes, and is the main reason we still don’t
> send failure mails to the commiter (and instead to me).
> But the real reason why the Travis setup is currently unusable is this:
>         Unexpected failures:
>            driver               T2507 [bad stderr] (normal)
>            driver               T8959a [bad stderr] (normal)
>            ghc-api              T6145 [bad exit code] (normal)
>            ghc-api              T8639_api [bad exit code] (normal)
>            ghc-api/annotations  T10278 [bad exit code] (normal)
>            ghc-api/annotations  T10357 [bad exit code] (normal)
>            ghc-api/annotations  T10358 [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)
> all of which fail with
>         collect2: ld terminated with signal 9 [Killed]
>         make[3]: *** [t10358] Error 1
> Unfortunately, when this first appeared, there were other build failures
> in HEAD, so I could not (easily) identify the first commit causing
> this.
> I raised this on this list (“api annotations test failures”, May 15).
> Alan Zimmerman looked into it, but it seems without success.
> Greetings,
> Joachim
> --
> Joachim “nomeata” Breitner
>   mail at joachim-breitner.de
>   Jabber: nomeata at  • GPG-Key: 0xF0FBF51F
>   Debian Developer: nomeata at
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ghc-devs mailing list