Re: Is this test summary good or bad?

2006-07-12 Thread Simon Marlow
Joel Reymont wrote: On Jul 11, 2006, at 11:00 AM, Simon Marlow wrote: Which ones hang? Could you take one of the hanging tests, compile it with -debug, run with +RTS -Ds, and send us the output? What ends up happening is this: 28683 p2 S 0:00.11 ../../timeout/timeout 300 cd ./typec

Re: Is this test summary good or bad?

2006-07-11 Thread Joel Reymont
On Jul 11, 2006, at 11:00 AM, Simon Marlow wrote: Which ones hang? Could you take one of the hanging tests, compile it with -debug, run with +RTS -Ds, and send us the output? What ends up happening is this: 28683 p2 S 0:00.11 ../../timeout/timeout 300 cd ./typecheck/ should_compile &

Re: Is this test summary good or bad?

2006-07-11 Thread Simon Marlow
Joel Reymont wrote: It's a little bit more complicated for me since some tests just plain hang. I will investigate, though. Which ones hang? Could you take one of the hanging tests, compile it with -debug, run with +RTS -Ds, and send us the output? Cheers, Simon ___

Re: Is this test summary good or bad?

2006-07-11 Thread Joel Reymont
It's a little bit more complicated for me since some tests just plain hang. I will investigate, though. On Jul 11, 2006, at 2:56 AM, Donald Bruce Stewart wrote: Not too bad (mips64 is around the same), but not the same as the linux head: [...] So the next step would be to diff the two resul

Re: Is this test summary good or bad?

2006-07-10 Thread Donald Bruce Stewart
joelr1: > This is using stage2. Does it look any better? > > OVERALL SUMMARY for test run started at Mon Jul 10 15:11:22 BST 2006 > 952 total tests, which gave rise to > 4583 test cases, of which > 11 caused framework failures > 1099 were skipped > > 3185 expected passes >

Re: Is this test summary good or bad?

2006-07-10 Thread Joel Reymont
This is using stage2. Does it look any better? OVERALL SUMMARY for test run started at Mon Jul 10 15:11:22 BST 2006 952 total tests, which gave rise to 4583 test cases, of which 11 caused framework failures 1099 were skipped 3185 expected passes 24 expected failures

Re: Is this test summary good or bad?

2006-07-10 Thread Simon Marlow
Joel Reymont wrote: On Jul 10, 2006, at 2:29 PM, Donald Bruce Stewart wrote: Using the wrong stage for the test? You'll need to use the stage2 ghc. make stage=2 does it but I wish this was documented. wish granted :-) Simon ___ Glasgow-haskell-

Re: Is this test summary good or bad?

2006-07-10 Thread Joel Reymont
On Jul 10, 2006, at 2:29 PM, Donald Bruce Stewart wrote: Using the wrong stage for the test? You'll need to use the stage2 ghc. make stage=2 does it but I wish this was documented. -- http://wagerlabs.com/ ___ Glasgow-haskell-users mailing lis

Re: Is this test summary good or bad?

2006-07-10 Thread Joel Reymont
On Jul 10, 2006, at 2:29 PM, Donald Bruce Stewart wrote: Using the wrong stage for the test? You'll need to use the stage2 ghc. How do I do this? I just ran make in the tests directory and it indeed picked up stage1 ghc. Thanks, Joel -- http://wagerlabs.com/ ___

Re: Is this test summary good or bad?

2006-07-10 Thread Donald Bruce Stewart
dons: > joelr1: > > Folks, > > > > I'm running Mac OSX 10.4.7 on Intel. This is the result of running > > the ghc-regress suite of tests using a freshly updated ghc 6.5 that > > was bootstrapped using a binary distribution. > > > > I suspect the framework failures were cases where tests got

Re: Is this test summary good or bad?

2006-07-10 Thread Donald Bruce Stewart
joelr1: > Folks, > > I'm running Mac OSX 10.4.7 on Intel. This is the result of running > the ghc-regress suite of tests using a freshly updated ghc 6.5 that > was bootstrapped using a binary distribution. > > I suspect the framework failures were cases where tests got hung and > I had to

Is this test summary good or bad?

2006-07-10 Thread Joel Reymont
Folks, I'm running Mac OSX 10.4.7 on Intel. This is the result of running the ghc-regress suite of tests using a freshly updated ghc 6.5 that was bootstrapped using a binary distribution. I suspect the framework failures were cases where tests got hung and I had to Ctrl-C them to let tes