On 28/02/2012 09:03, Simon Marlow wrote:
The safeHaskell failures disappeared on my second validate run, so I'm
not sure what happened (I had pulled into the tree first, and there were
no patches between the two runs that should have affected this). Perhaps
there's some missing cleaning somewhere? Anyway I wouldn't worry about
it unless the failures come back.
I just remembered: my second validate was with --fast, so it seems the
safeHaskell failures only show up without --fast. Probably some bad
interaction with BINARY_DIST=YES?
Cheers,
Simon
The other failures were still there though...
Cheers,
Simon
On 28/02/2012 04:54, David Terei wrote:
Is this still happening and on what platforms? I don't get the
safeHaskell failures on X64 Linux....
Cheers,
David
On 27 February 2012 06:09, Simon Marlow<[email protected]> wrote:
Validate is slipping again folks. Can those responsible please clean
up the
failures? These make it hard for someone else to figure out whether they
can commit or not.
Unexpected failures:
ghci/scripts Defer02 [bad stderr] (ghci)
indexed-types/should_fail T3330c [stderr mismatch] (normal)
polykinds PolyKinds02 [stderr mismatch] (normal)
safeHaskell/ghci p5 [bad stdout] (ghci)
safeHaskell/ghci p7 [bad stdout] (ghci)
safeHaskell/ghci p8 [bad stdout] (ghci)
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
