ghc-testsuite-6.6 on Macs
Did someone run the test-suite of the binary distributions? http://www.haskell.org/ghc/dist/6.6/ghc-6.6-ppc-apple-darwin.tar.gz http://www.haskell.org/ghc/dist/6.6/ghc-6.6-i386-apple-darwin.tar.bz2 I've build a (ppc-) mac-distribution from sources and my results are shown below. I had the following 3 unexpected failures under linux, too (by using "make TEST_HC=<installed ghc>" and the <installed ghc> was from http://www.haskell.org/ghc/dist/6.6/ghc-6.6-i386-unknown-linux.tar.bz2) cg058(ghci) ghcpkg01(normal) ghcpkg03(normal) I thought the failure signals002(ghci) was related to http://article.gmane.org/gmane.comp.lang.haskell.glasgow.user/10947 In fact, I needed to kill the ghc-process to continue the tests. The test files cc004.hs and ffi012.hs failed with several messages of the form: calling convention not supported on this architecture: stdcall When checking declaration: foreign import stdcall safe "wrapper" wrap_f :: F -> IO (FunPtr F) However, they did not make it into the summary Cheers Christian OVERALL SUMMARY for test run started at Mon Oct 23 14:54:15 CEST 2006 1455 total tests, which gave rise to 6441 test cases, of which 0 caused framework failures 1126 were skipped 5242 expected passes 55 expected failures 3 unexpected passes 15 unexpected failures Unexpected passes: barton-mangler-bug(optasm) cholewo-eval(optasm,profasm) Unexpected failures: barton-mangler-bug(opt) cabal02(normal) cg058(ghci) conc019(opt,profasm) conc024(opt) ffi009(ghci) forkprocess01(ghci) galois_raytrace(opt,prof) ghcpkg01(normal) ghcpkg03(normal) joao-circular(prof,profasm) signals002(ghci)
Christian Maeder schrieb:
Did someone run the test-suite of the binary distributions?
http://www.haskell.org/ghc/dist/6.6/ghc-6.6-i386-apple-darwin.tar.bz2
This distribution on our MacIntel produced the following summary in a newly made ghc-6.6 sources tree with TEST_HC=<installed ghc>": OVERALL SUMMARY for test run started at Wed Nov 1 18:06:39 CET 2006 1455 total tests, which gave rise to 6918 test cases, of which 0 caused framework failures 1178 were skipped 5660 expected passes 56 expected failures 0 unexpected passes 24 unexpected failures Unexpected failures: conc019(normal,optasm,prof,profasm) conc024(prof,profasm) conc049(optasm) ffi009(threaded1) ffi012(normal,opt,optasm,prof,profasm,ghci,threaded1,threaded2) ffi016(normal,opt,optasm) ghcpkg01(normal) ghcpkg03(normal) memo001(threaded1) net001(threaded2) signals002(ghci) conc019 failed with: caught: thread blocked indefinitely and con024: thread blocked indefinitely
Christian Maeder wrote:
Did someone run the test-suite of the binary distributions?
http://www.haskell.org/ghc/dist/6.6/ghc-6.6-ppc-apple-darwin.tar.gz http://www.haskell.org/ghc/dist/6.6/ghc-6.6-i386-apple-darwin.tar.bz2
I've build a (ppc-) mac-distribution from sources and my results are shown below.
I had the following 3 unexpected failures under linux, too (by using "make TEST_HC=<installed ghc>" and the <installed ghc> was from http://www.haskell.org/ghc/dist/6.6/ghc-6.6-i386-unknown-linux.tar.bz2)
cg058(ghci)
We also have cg058(ghci) failing on x86, I think it just runs out of time. We should make this test a bit quicker.
ghcpkg01(normal) ghcpkg03(normal)
Any idea why these are failing for you?
I thought the failure signals002(ghci) was related to http://article.gmane.org/gmane.comp.lang.haskell.glasgow.user/10947 In fact, I needed to kill the ghc-process to continue the tests.
The test files cc004.hs and ffi012.hs failed with several messages of the form:
calling convention not supported on this architecture: stdcall When checking declaration: foreign import stdcall safe "wrapper" wrap_f :: F -> IO (FunPtr F)
However, they did not make it into the summary
They are probably expected failures for you.
Cheers Christian
OVERALL SUMMARY for test run started at Mon Oct 23 14:54:15 CEST 2006 1455 total tests, which gave rise to 6441 test cases, of which 0 caused framework failures 1126 were skipped
5242 expected passes 55 expected failures 3 unexpected passes 15 unexpected failures
Unexpected passes: barton-mangler-bug(optasm) cholewo-eval(optasm,profasm)
Unexpected failures: barton-mangler-bug(opt) cabal02(normal) cg058(ghci) conc019(opt,profasm) conc024(opt) ffi009(ghci) forkprocess01(ghci) galois_raytrace(opt,prof) ghcpkg01(normal) ghcpkg03(normal) joao-circular(prof,profasm) signals002(ghci)
some of those could be floating-point differences. In any case, it would be good to investigate all of them and get any expected failures registered properly in the testsuite. Can you (or someone else) take a look and find out why each of them is failing? Cheers, Simon
Simon Marlow schrieb:
ghcpkg01(normal) ghcpkg03(normal)
Any idea why these are failing for you?
Maybe rather than using my installed ghc-pkg (that lists haskell-src) some inplace ghc-pkg was used: ghc-pkg: dependency haskell-src doesn't exist (use --force to override) make[2]: *** [ghcpkg01] Fehler 1
I thought the failure signals002(ghci) was related to http://article.gmane.org/gmane.comp.lang.haskell.glasgow.user/10947 In fact, I needed to kill the ghc-process to continue the tests.
The test files cc004.hs and ffi012.hs failed with several messages of the form:
calling convention not supported on this architecture: stdcall When checking declaration: foreign import stdcall safe "wrapper" wrap_f :: F -> IO (FunPtr F)
However, they did not make it into the summary
They are probably expected failures for you.
Yes they are indeed, but should these really be "expected failures"?
some of those could be floating-point differences. In any case, it would be good to investigate all of them and get any expected failures registered properly in the testsuite. Can you (or someone else) take a look and find out why each of them is failing?
Yes, I hope someone else joins in. Christian
Hello, This is an attempt to address (a very small part of) this: On my PowerPC Mac OS X 10.3 (Panther, I think, not Tiger as I have written elsewhere), I have built the ghc-6.6 branch (of about 2006-Nov-07 19.00 UTC) using GHC-6.4.1.pkg.zip (The Glorious Glasgow Haskell Compilation System, version 6.4.1) that I got from http://haskell.org/ghc/download_ghc_641.html. I haven't studied the details of Cabal yet, so to work around an X11 problem (http://www.haskell.org/pipermail/cvs-ghc/2006-November/032492.html), I did (1) darcs get of the ghc-6.6 branch; (2) sh darcs-all get (without --extra); (3) got through gmake of everything without failing; (4) sh darcs-all --extra get (to get the extra libraries, some of which (e.g. QuickCheck) are needed for some of the tests); and finally (5) repeated gmake of everything, failing at the X11 build, but getting through the QuickCheck build. Then I "darcs got" the ghc-6.6/testsuite and ran the tests. My hope was that I would be able to reproduce something similar to http://www.haskell.org/pipermail/glasgow-haskell-users/2006-October/011457.h..., although under different circumstances. So far, I have only analysed the barton-mangler-bug test in detail. I have produced an experimental darcs patch that solves some problems, while possibly introducing others: http://thorkilnaur.dk/~tn/GHC/testsuite/patch/barton_mangler_bug_patch_1.pat... . Comments to this would be most welcome. Best regards Thorkil On Tuesday 07 November 2006 12:39, Christian Maeder wrote:
Simon Marlow schrieb:
ghcpkg01(normal) ghcpkg03(normal)
Any idea why these are failing for you?
Maybe rather than using my installed ghc-pkg (that lists haskell-src) some inplace ghc-pkg was used:
ghc-pkg: dependency haskell-src doesn't exist (use --force to override) make[2]: *** [ghcpkg01] Fehler 1
I thought the failure signals002(ghci) was related to http://article.gmane.org/gmane.comp.lang.haskell.glasgow.user/10947 In fact, I needed to kill the ghc-process to continue the tests.
The test files cc004.hs and ffi012.hs failed with several messages of the form:
calling convention not supported on this architecture: stdcall When checking declaration: foreign import stdcall safe "wrapper" wrap_f :: F -> IO (FunPtr F)
However, they did not make it into the summary
They are probably expected failures for you.
Yes they are indeed, but should these really be "expected failures"?
some of those could be floating-point differences. In any case, it would be good to investigate all of them and get any expected failures registered properly in the testsuite. Can you (or someone else) take a look and find out why each of them is failing?
Yes, I hope someone else joins in. Christian
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Simon Marlow schrieb:
Christian Maeder wrote:
The test files cc004.hs and ffi012.hs failed with several messages of the form:
calling convention not supported on this architecture: stdcall When checking declaration: foreign import stdcall safe "wrapper" wrap_f :: F -> IO (FunPtr F)
However, they did not make it into the summary
They are probably expected failures for you.
Also the following output is expected. I hope it's no error in Data.HashTab or the desugarer? Cheers Christian =====> maessen_hashtab(normal) cd ./programs/maessen-hashtab && '/home/maeder/haskell/pc-solaris/ghc-6.6/compiler/stage2/ghc-inplace' -no-recomp -dcore-lint -dcmm-lint -Di386_unknown_solaris2 --make -o maessen_hashtab HashTest -cpp >maessen_hashtab.comp.stderr 2>&1 Compile failed (status 256) errors were: [1 of 2] Compiling Data.HashTab ( Data/HashTab.hs, Data/HashTab.o ) [2 of 2] Compiling Main ( HashTest.hs, HashTest.o ) *** Core Lint Errors: in result of Desugar *** <no location info>: In the expression: Data.HashTab.update @ GHC.Base.Int @ GHC.Base.Int ht_a4UG Argument value doesn't match argument type: Fun type: Data.HashTab.HashTable GHC.Base.Int GHC.Base.Int -> GHC.Base.Int -> GHC.Base.Int -> GHC.IOBase.IO GHC.Base.Bool Arg type: Main.HT Arg: ht_a4UG *** Offending Program *** [...]
This is a long-standing oddity. I have investigated it at least twice, and found out what is going on. Each time I do so, I think it's not important enough to fix today... and before I know it I've forgotten what the problem is again. I must write it down! Anyway, it happens on all platforms. Don't worry about it; but leave it as a failure so that I don't forget to attend to it Simon | =====> maessen_hashtab(normal) | cd ./programs/maessen-hashtab && | '/home/maeder/haskell/pc-solaris/ghc-6.6/compiler/stage2/ghc-inplace' | -no-recomp -dcore-lint -dcmm-lint -Di386_unknown_solaris2 | --make -o maessen_hashtab HashTest -cpp >maessen_hashtab.comp.stderr | 2>&1 | Compile failed (status 256) errors were: | [1 of 2] Compiling Data.HashTab ( Data/HashTab.hs, Data/HashTab.o ) | [2 of 2] Compiling Main ( HashTest.hs, HashTest.o ) | *** Core Lint Errors: in result of Desugar *** | <no location info>: | In the expression: Data.HashTab.update @ GHC.Base.Int @ GHC.Base.Int | ht_a4UG | Argument value doesn't match argument type: | Fun type: | Data.HashTab.HashTable GHC.Base.Int GHC.Base.Int | -> GHC.Base.Int | -> GHC.Base.Int | -> GHC.IOBase.IO GHC.Base.Bool | Arg type: Main.HT | Arg: ht_a4UG | *** Offending Program *** | [...] | | _______________________________________________ | Glasgow-haskell-users mailing list | Glasgow-haskell-users@haskell.org | http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
also tests/ghc-regress/programs/okeefe_neural is too big to simply fail with: Compile failed (status 256) errors were: ghc-6.6: unknown package: lang Christian
participants (4)
-
Christian Maeder -
Simon Marlow -
Simon Peyton-Jones -
Thorkil Naur