On 15/09/2011 01:16, GHC Build Reports wrote:
Unexpected failures:
codeGen/should_run cgrun059 [bad exit code]
(hpc,optasm,profasm,threaded2,dyn,profthreaded,optllvm)
deriving/should_fail T2701 [stderr mismatch] (normal)
driver 5313 [bad exit code] (ghci)
ghci.debugger/scripts 2740 [bad stdout] (ghci)
ghci.debugger/scripts break001 [bad stderr] (ghci)
ghci.debugger/scripts break005 [bad stdout] (ghci)
ghci.debugger/scripts break006 [bad stdout] (ghci)
ghci.debugger/scripts break026 [bad stdout] (ghci)
ghci.debugger/scripts break027 [bad stdout] (ghci)
ghci.debugger/scripts dynbrk002 [bad stdout] (ghci)
ghci.debugger/scripts print002 [bad stdout] (ghci)
ghci.debugger/scripts print003 [bad stderr] (ghci)
ghci.debugger/scripts print005 [bad stdout] (ghci)
ghci.debugger/scripts print006 [bad stderr] (ghci)
ghci.debugger/scripts print008 [bad stdout] (ghci)
ghci.debugger/scripts print012 [bad stdout] (ghci)
ghci.debugger/scripts print013 [bad stdout] (ghci)
ghci.debugger/scripts print014 [bad stderr] (ghci)
ghci/scripts 2976 [bad stdout] (ghci)
indexed-types/should_compile T4160 [exit code non-0] (profasm)
perf/compiler T4801 [stat too good] (normal)
plugins plugins05 [exit code non-0]
(profasm,dyn,profthreaded)
plugins plugins06 [exit code non-0]
(profasm,dyn,profthreaded)
rename/should_compile/T3103 T3103 [exit code non-0] (profasm)
Those ghci.debugger failures are new (since yesterday). I took a quick
look, and they all seem to be caused by the debugger deriving Integer
rather than an unknown type for some runtime variable - perhaps Integers
are evaluated more often now?
So the test results are probably ok, but I'm a little concerned that
some of these tests are not testing what they were before.
Ian, do you have outstanding patches to update the output for these?
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
