Windows failures

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Windows failures

Simon Peyton Jones
Ian
This is 'sh validate" on 64bit Windows.  Rather a lot of failures.  Might you look?

The perf tests seem to fail because it's comparing with the *32* bit numbers, even though this is definitely a *64* bit laptop.   Whether the entire build system thinks it's a 32 bit machine, or just the testsuite, I can't tell.

Thanks

Simon


Unexpected failures:
   cabal/cabal01            cabal01 [bad exit code] (normal)
   cabal/cabal04            cabal04 [bad exit code] (normal)
   driver                   dynHelloWorld [exit code non-0] (dyn)
   driver/dynamicToo        dynamicToo002 [bad stdout] (normal)
   driver/dynamicToo        dynamicToo003 [bad exit code] (normal)
   dynlibs                  T4464 [bad exit code] (normal)
   dynlibs                  T5373 [bad exit code] (normal)
   ghc-api/T7478            T7478 [bad exit code] (normal)
   ghci.debugger/scripts    break008 [bad exit code] (ghci)
   ghci.debugger/scripts    dynbrk009 [bad exit code] (ghci)
   ghci/scripts             T5975a [bad stderr] (ghci)
   llvm/should_compile      T5486 [exit code non-0] (optllvm)
   llvm/should_compile      T5681 [exit code non-0] (optllvm)
   llvm/should_compile      T6158 [exit code non-0] (optllvm)
   llvm/should_compile      T7571 [exit code non-0] (optllvm)
   llvm/should_compile      T7575 [exit code non-0] (optllvm)
   perf/compiler            T1969 [stat not good enough] (normal)
   perf/compiler            T3294 [stat not good enough] (normal)
   perf/compiler            T4801 [stat too good] (normal)
   perf/haddock             haddock.Cabal [stat not good enough] (normal)
   perf/haddock             haddock.base [stat not good enough] (normal)
   perf/haddock             haddock.compiler [stat not good enough] (normal)
   perf/should_run          T7797 [stat too good] (normal)
   rts                      T4850 [bad stdout] (normal)
   rts                      derefnull [bad exit code] (normal)
   rts                      divbyzero [bad exit code] (normal)
   runghc                   T7859 [bad stderr] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly01 [exit code non-0] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly02 [exit code non-0] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly03 [stderr mismatch] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly04 [exit code non-0] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly05 [stderr mismatch] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly06 [exit code non-0] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly07 [stderr mismatch] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly08 [stderr mismatch] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly09 [stderr mismatch] (normal)
   safeHaskell/check/pkg01  ImpSafeOnly10 [exit code non-0] (normal)
   safeHaskell/check/pkg01  safePkg01 [bad exit code] (normal)


Reply | Threaded
Open this post in threaded view
|

Windows failures

Ian Lynagh-2
On Mon, Jun 17, 2013 at 08:48:15PM +0000, Simon Peyton-Jones wrote:
> This is 'sh validate" on 64bit Windows.  Rather a lot of failures.  Might you look?

Sure.

> The perf tests seem to fail because it's comparing with the *32* bit numbers, even though this is definitely a *64* bit laptop.   Whether the entire build system thinks it's a 32 bit machine, or just the testsuite, I can't tell.

If you have a 64bit Windows machine, then you'll be able to run both the
32bit and 64bit GHC builds. If you run "ghc --info | grep Target" then
you'll see which is being used - it'll say x86_64-unknown-mingw32 if
it's 64bit, and i386-unknown-mingw32 if it's 32bit. I suspect that you
have a 32bit GHC, so comparing with the 32bit numbers is right. They
probably just need updating for recent wobbles.


Thanks
Ian
--
Ian Lynagh, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/


Reply | Threaded
Open this post in threaded view
|

Windows failures

Simon Peyton Jones
Curiously you are right.  Target is
,("Target platform","i386-unknown-mingw32")

Weird since it's a 64-bit machine.

Simon

-----Original Message-----
From: Ian Lynagh [mailto:ian at well-typed.com]
Sent: 18 June 2013 23:06
To: Simon Peyton-Jones
Cc: ghc-devs at haskell.org
Subject: Re: Windows failures

On Mon, Jun 17, 2013 at 08:48:15PM +0000, Simon Peyton-Jones wrote:
> This is 'sh validate" on 64bit Windows.  Rather a lot of failures.  Might you look?

Sure.

> The perf tests seem to fail because it's comparing with the *32* bit numbers, even though this is definitely a *64* bit laptop.   Whether the entire build system thinks it's a 32 bit machine, or just the testsuite, I can't tell.

If you have a 64bit Windows machine, then you'll be able to run both the 32bit and 64bit GHC builds. If you run "ghc --info | grep Target" then you'll see which is being used - it'll say x86_64-unknown-mingw32 if it's 64bit, and i386-unknown-mingw32 if it's 32bit. I suspect that you have a 32bit GHC, so comparing with the 32bit numbers is right. They probably just need updating for recent wobbles.


Thanks
Ian
--
Ian Lynagh, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/