I don&#39;t know what -fghci-leak-check does at all, but if they are to be expected we shouldn&#39;t accept the changes. Instead change the default options in the testsuite to pass -fno-ghci-leak-check (I assume that exists) <div><br><div class="gmail_quote"><div dir="ltr">On Thu, May 31, 2018, 06:49 Ryan Scott &lt;<a href="mailto:ryan.gl.scott@gmail.com">ryan.gl.scott@gmail.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>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:</div><div><br></div><div>Unexpected failures:<br>   ghci/prog001/prog001.run            prog001 [bad stdout] (ghci)<br>   ghci/prog002/prog002.run            prog002 [bad stdout] (ghci)<br>   ghci/prog003/prog003.run            prog003 [bad stdout] (ghci)<br>   ghci/prog010/ghci.prog010.run       ghci.prog010 [bad stdout] (ghci)<br>   ghci/prog013/prog013.run            prog013 [bad stdout] (ghci)<br>   ghci/prog012/prog012.run            prog012 [bad stdout] (ghci)<br>   ghci/prog009/ghci.prog009.run       ghci.prog009 [bad stdout] (ghci)<br>   ghci/scripts/ghci025.run            ghci025 [bad stdout] (ghci)<br>   ghci/scripts/ghci038.run            ghci038 [bad stdout] (ghci)<br>   ghci/scripts/ghci057.run            ghci057 [bad stdout] (ghci)<br>   ghci/scripts/T2182ghci.run          T2182ghci [bad stdout] (ghci)<br>   ghci/scripts/ghci058.run            ghci058 [bad stdout] (ghci)<br>   ghci/scripts/T6106.run              T6106 [bad stdout] (ghci)<br>   ghci/scripts/T8353.run              T8353 [bad stdout] (ghci)<br>   ghci/scripts/T9293.run              T9293 [bad stdout] (ghci)<br>   ghci/scripts/T10989.run             T10989 [bad stdout] (ghci)<br>   ghci/should_run/T13825-ghci.run     T13825-ghci [bad stdout] (ghci)<br>   ghci.debugger/scripts/print007.run  print007 [bad stdout] (ghci)<br>   ghci.debugger/scripts/break009.run  break009 [bad stdout] (ghci)<br>   ghci.debugger/scripts/break008.run  break008 [bad stdout] (ghci)<br>   ghci.debugger/scripts/break026.run  break026 [bad stdout] (ghci)<br>   perf/space_leaks/T4029.run          T4029 [bad stdout] (ghci)</div><div><br></div><div>And the full failing test output can be found here [1]. (I won&#39;t post it inline, since it&#39;s quite large).</div><div><br></div><div>Are these changes expected? I&#39;m not at all familiar with -fghci-leak-check, so I don&#39;t know if we should accept the new output or not.<br></div><div><br></div><div>Ryan S.</div><div>-----</div><div>[1] <a href="https://gist.githubusercontent.com/RyanGlScott/f920737287049b82947e1c47cdbc2b94/raw/4fe68d47cc78675424e09cf451be556c6f430d08/gistfile1.txt" target="_blank">https://gist.githubusercontent.com/RyanGlScott/f920737287049b82947e1c47cdbc2b94/raw/4fe68d47cc78675424e09cf451be556c6f430d08/gistfile1.txt</a><br></div></div>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</blockquote></div></div>