Re: -fghci-leak-check apparently causes many tests to fail
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 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.runprog002 [bad stdout] (ghci) >ghci/prog003/prog003.runprog003 [bad stdout] (ghci) >ghci/prog010/ghci.prog010.run ghci.prog010 [bad stdout] (ghci) >ghci/prog013/prog013.runprog013 [bad stdout] (ghci) >ghci/prog012/prog012.runprog012 [bad stdout] (ghci) >ghci/prog009/ghci.prog009.run ghci.prog009 [bad stdout] (ghci) >ghci/scripts/ghci025.runghci025 [bad stdout] (ghci) >ghci/scripts/ghci038.runghci038 [bad stdout] (ghci) >ghci/scripts/ghci057.runghci057 [bad stdout] (ghci) >ghci/scripts/T2182ghci.run T2182ghci [bad stdout] (ghci) >ghci/scripts/ghci058.runghci058 [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@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Trac email
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, > > 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> wrote: > >> 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 >> > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Trac email
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> wrote: > 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 > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Trac email
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
-fghci-leak-check apparently causes many tests to fail
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.runprog002 [bad stdout] (ghci) ghci/prog003/prog003.runprog003 [bad stdout] (ghci) ghci/prog010/ghci.prog010.run ghci.prog010 [bad stdout] (ghci) ghci/prog013/prog013.runprog013 [bad stdout] (ghci) ghci/prog012/prog012.runprog012 [bad stdout] (ghci) ghci/prog009/ghci.prog009.run ghci.prog009 [bad stdout] (ghci) ghci/scripts/ghci025.runghci025 [bad stdout] (ghci) ghci/scripts/ghci038.runghci038 [bad stdout] (ghci) ghci/scripts/ghci057.runghci057 [bad stdout] (ghci) ghci/scripts/T2182ghci.run T2182ghci [bad stdout] (ghci) ghci/scripts/ghci058.runghci058 [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@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
