validate test failures

[Manuel M T Chakravarty]

David Terei:
> The Safe Haskell ones have been fixed a couple of hours back, if you
> pull the latest testsuite but are getting failure let me know.

One of my repos somehow forgot which remote it was tracking, which stopped ./sync-all prematurely — so, it didn't pull all repos.

Sorry,
Manuel

> On 9 August 2011 22:03, Manuel M T Chakravarty <chak at cse.unsw.edu.au> wrote:
>> A few days ago, I had zero failures on OS X, now I have
>> 
>>> Unexpected passes:
>>>    th/TH_recompile  TH_recompile (normal)
>>> 
>>> Unexpected failures:
>>>    cabal                    ghcpkg01 [bad stdout] (normal)
>>>    ghci/scripts             T4127 [bad stdout] (ghci)
>>>    module                   mod90 [stderr mismatch] (normal)
>>>    safeHaskell/check        Check01 [exit code 0] (normal)
>>>    safeHaskell/check/pkg01  ImpSafe01 [exit code 0] (normal)
>>>    safeHaskell/check/pkg01  ImpSafeOnly03 [exit code 0] (normal)
>>>    safeHaskell/check/pkg01  safePkg01 [bad stdout] (normal)
>>>    th                       T3572 [bad stdout] (normal)
>>>    th                       T3920 [bad stdout] (normal)
>>>    th                       T5037 [stderr mismatch] (normal)
>>>    th                       TH_ppr1 [bad stdout] (normal)
>>>    th                       TH_repGuard [stderr mismatch] (normal)
>>>    th                       TH_viewPatPrint [bad stdout] (normal)
>> 
>> They all seem to be related to SafeHaskell (changes in .cabal files from packages being trusted) and TH (minor wobbles to identifiers in the output).
> 
> _______________________________________________
> Cvs-ghc mailing list
> Cvs-ghc at haskell.org
> http://www.haskell.org/mailman/listinfo/cvs-ghc