<div dir="ltr"><div><div>Your mail seems to indicate that the processes were sent a SIGKILL during the link phase.<br><br></div>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.<br><br></div><div>I suspect the timeout is not the culprit.<br><br></div><div>Is there any way to check for out of memory kills on the travis box?<br><br></div><div>Or is there another way it can be killed?<br><br></div><div>Alan<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 29, 2015 at 10:42 PM, Joachim Breitner <span dir="ltr"><<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Am Donnerstag, den 28.05.2015, 17:46 -0700 schrieb Edward Z. Yang:<br>
> To whoever manages our Travis setup <a href="https://travis-ci.org/ghc/ghc/builds" target="_blank">https://travis-ci.org/ghc/ghc/builds</a><br>
<br>
that would be me.<br>
<br>
> We seem to be failing because our build takes longer than 50min.<br>
<br>
that happens occasionally, yes, and is the main reason we still don’t<br>
send failure mails to the commiter (and instead to me).<br>
<br>
But the real reason why the Travis setup is currently unusable is this:<br>
<br>
Unexpected failures:<br>
driver T2507 [bad stderr] (normal)<br>
driver T8959a [bad stderr] (normal)<br>
ghc-api T6145 [bad exit code] (normal)<br>
ghc-api T8639_api [bad exit code] (normal)<br>
ghc-api/annotations T10278 [bad exit code] (normal)<br>
ghc-api/annotations T10357 [bad exit code] (normal)<br>
ghc-api/annotations T10358 [bad exit code] (normal)<br>
ghc-api/annotations T10396 [bad exit code] (normal)<br>
ghc-api/annotations T10399 [bad exit code] (normal)<br>
ghc-api/annotations boolFormula [bad exit code] (normal)<br>
<br>
all of which fail with<br>
<br>
collect2: ld terminated with signal 9 [Killed]<br>
make[3]: *** [t10358] Error 1<br>
<br>
<br>
Unfortunately, when this first appeared, there were other build failures<br>
in HEAD, so I could not (easily) identify the first commit causing<br>
this.<br>
<br>
I raised this on this list (“api annotations test failures”, May 15).<br>
Alan Zimmerman looked into it, but it seems without success.<br>
<br>
<br>
<br>
Greetings,<br>
Joachim<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Joachim “nomeata” Breitner<br>
<a href="mailto:mail@joachim-breitner.de">mail@joachim-breitner.de</a> • <a href="http://www.joachim-breitner.de/" target="_blank">http://www.joachim-breitner.de/</a><br>
Jabber: <a href="mailto:nomeata@joachim-breitner.de">nomeata@joachim-breitner.de</a> • GPG-Key: 0xF0FBF51F<br>
Debian Developer: <a href="mailto:nomeata@debian.org">nomeata@debian.org</a><br>
</font></span><br>_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
<br></blockquote></div><br></div>