-fghci-leak-check apparently causes many tests to fail

Phyx lonetiger at gmail.com
Thu May 31 21:53:46 UTC 2018

I don't know what -fghci-leak-check does at all, but if they are to be
expected we shouldn't accept the changes. Instead change the default
options in the testsuite to pass -fno-ghci-leak-check (I assume that

On Thu, May 31, 2018, 06:49 Ryan Scott <ryan.gl.scott at gmail.com> wrote:

> I recently ran the testsuite and experienced a very large number of
> testsuite failures, all of which seem to involve the new -fghci-leak-check
> flag. Here is the list of tests that fail:
> Unexpected failures:
>    ghci/prog001/prog001.run            prog001 [bad stdout] (ghci)
>    ghci/prog002/prog002.run            prog002 [bad stdout] (ghci)
>    ghci/prog003/prog003.run            prog003 [bad stdout] (ghci)
>    ghci/prog010/ghci.prog010.run       ghci.prog010 [bad stdout] (ghci)
>    ghci/prog013/prog013.run            prog013 [bad stdout] (ghci)
>    ghci/prog012/prog012.run            prog012 [bad stdout] (ghci)
>    ghci/prog009/ghci.prog009.run       ghci.prog009 [bad stdout] (ghci)
>    ghci/scripts/ghci025.run            ghci025 [bad stdout] (ghci)
>    ghci/scripts/ghci038.run            ghci038 [bad stdout] (ghci)
>    ghci/scripts/ghci057.run            ghci057 [bad stdout] (ghci)
>    ghci/scripts/T2182ghci.run          T2182ghci [bad stdout] (ghci)
>    ghci/scripts/ghci058.run            ghci058 [bad stdout] (ghci)
>    ghci/scripts/T6106.run              T6106 [bad stdout] (ghci)
>    ghci/scripts/T8353.run              T8353 [bad stdout] (ghci)
>    ghci/scripts/T9293.run              T9293 [bad stdout] (ghci)
>    ghci/scripts/T10989.run             T10989 [bad stdout] (ghci)
>    ghci/should_run/T13825-ghci.run     T13825-ghci [bad stdout] (ghci)
>    ghci.debugger/scripts/print007.run  print007 [bad stdout] (ghci)
>    ghci.debugger/scripts/break009.run  break009 [bad stdout] (ghci)
>    ghci.debugger/scripts/break008.run  break008 [bad stdout] (ghci)
>    ghci.debugger/scripts/break026.run  break026 [bad stdout] (ghci)
>    perf/space_leaks/T4029.run          T4029 [bad stdout] (ghci)
> And the full failing test output can be found here [1]. (I won't post it
> inline, since it's quite large).
> Are these changes expected? I'm not at all familiar with
> -fghci-leak-check, so I don't know if we should accept the new output or
> not.
> Ryan S.
> -----
> [1]
> https://gist.githubusercontent.com/RyanGlScott/f920737287049b82947e1c47cdbc2b94/raw/4fe68d47cc78675424e09cf451be556c6f430d08/gistfile1.txt
> _______________________________________________
> 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/20180531/e6336374/attachment.html>

More information about the ghc-devs mailing list