New GHCi failures

Simon Marlow marlowsd at gmail.com
Mon Feb 13 13:50:31 CET 2012


As of the nightly build on 11 Feb, we have three new GHCi-related test 
failures:

   ghci/prog009                             ghci.prog009 [bad stdout] (ghci)
   ghci/scripts                             ghci036 [bad stderr] (ghci)
   ghci/scripts                             ghci038 [bad stderr] (ghci)

I haven't narrowed it down to a specific patch, but these are strong 
contenders:

commit b23a7e55feb055f8b309ec3b5bb34526d951e969
Author: David Terei <davidterei at gmail.com>
Date:   Wed Feb 8 17:24:49 2012 -0800

     Don't allow implicit qualified imports in GHCi when -XSafe on.

     It would be better to actually check the safety of the import but doing
     that requires some significant refactoring of code so punting for
     another day.

commit e5272d9bf2a65b7da8364803fcafbd2012b7de97
Author: David Terei <davidterei at gmail.com>
Date:   Wed Feb 8 18:35:54 2012 -0800

     Don't add a bad import to the saved context.

     Importing an unsafe module in GHCi under -XSafe would fail
     but still save that in the context so it would be retried
     on every subsequent import.


David, could you check please?

Cheers,
	Simon



More information about the Cvs-ghc mailing list