These safe haskell failures are all fixed now:
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 std
OK the Safe Haskell problem is fixed. Great.
I get the following failures on Windows. Soe of them (eg environment001) have
been failing for some time. Something Unicode related.
The entire test framework has some kind of Python failure. I've seen this
before too, but I'm not sure what it me
Thanks. I dumped the info into http://hackage.haskell.org/trac/ghc/ticket/5338
Simon
From: Ryan Newton [mailto:rrnew...@gmail.com]
Sent: 21 July 2011 22:23
To: Simon Peyton-Jones
Cc: cvs-ghc@haskell.org
Subject: Re: windows failures
Ah ok. Is there a ticket mentioning Ian's suggested fix?
I’m getting these failures on my 32-bit windows machine.
Unexpected failures:
../../libraries/random/tests rangeTest [bad exit code] (normal)
cabal ghcpkg03 [bad stderr] (normal)
lib/IO3307 [bad exit code] (normal)
lib/IO
On Thu, Apr 14, 2011 at 03:12:58PM +, Simon Peyton-Jones wrote:
> I'm getting these failures on Windows that don't seem related to line endings.
>
> Are others getting them?
I've just validated on msys. I see ffi022 failing, but not 3236 or
bytestring003.
Thanks
Ian
__
I'm getting these failures on Windows that don't seem related to line endings.
Are others getting them?
Simon
=> 3236(normal) 1873 of 2703 [3, 11, 0]
cd ./rts && 'C:/code/HEAD-git/bindisttest/install dir/bin/ghc.exe'
-fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-c
Tue Jan 22 08:05:46 PST 2008 Simon Marlow <[EMAIL PROTECTED]>
* normalise '\' to '/' in the output, to fix Windows failures
M ./tests/ghc-regress/ghci.debugger/scripts/all.T -1 +1
___
Cvs-ghc mailing lis
