Travis builds failing

[Alan & Kim Zimmerman]

I think the annotations tests are failing because the Makefile looks like
this (excerpt)

-------------------
CheckAnnotations: CheckAnnotations.hs
    rm -f CheckAnnotations CheckAnnotations.hi CheckAnnotations.o
    '$(TEST_HC)' $(TEST_HC_OPTS) --make -w -v0 -package ghc CheckAnnotations

.PHONY: T10358
T10358: CheckAnnotations
    ./CheckAnnotations "`'$(TEST_HC)' $(TEST_HC_OPTS) --print-libdir | tr
-d '\r'`" Test10358

.PHONY: T10396
T10396: CheckAnnotations
    ./CheckAnnotations "`'$(TEST_HC)' $(TEST_HC_OPTS) --print-libdir | tr
-d '\r'`" Test10396
------------------------

If separate processes are used to execute "make T10396" and "make T10358",
they will each independently try to build CheckAnnotations.

This causes problems.

Alan


On Sat, May 30, 2015 at 12:00 PM, Alan & Kim Zimmerman <alan.zimm at gmail.com>
wrote:

> 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?
>
> Alan
>
>
> On Fri, May 29, 2015 at 10:42 PM, Joachim Breitner <
> mail at joachim-breitner.de> wrote:
>
>> Hi,
>>
>> Am Donnerstag, den 28.05.2015, 17:46 -0700 schrieb Edward Z. Yang:
>> > To whoever manages our Travis setup
>> https://travis-ci.org/ghc/ghc/builds
>>
>> 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 • 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20150530/872a5391/attachment.html>