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
exists)
On Thu, May 31, 2018, 06:49 Ryan Scott wrote:
> I recently ran the testsuite an
The mail servers were backed up with spam apparently. No emails were
delivered or received to any of the mailing lists
https://www.reddit.com/r/haskell/comments/8mza0y/whats_up_with_mailhaskellorg_dark_since_sunday/
Cheers,
Tamar
On Thu, May 31, 2018, 15:26 Artem Pelenitsyn
wrote:
> Hello,
>
>
Hello,
It stopped working for me from like Sunday and wasn't working for about two
days. Then, on Tuesday, it silently started working again. Although, I
haven't checked that I get all the emails.
--
Best, Artem
On Thu, 31 May 2018, 21:13 Simon Peyton Jones via ghc-devs, <
ghc-devs@haskell.org>
Devs
Trac has entirely stopped sending me email, so I have no idea what's happening
on the GHC front. Could someone unglue it?
Thanks!
Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
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.runprog001 [bad stdout] (ghci)
ghci/prog002/prog002.
