[Last night's post got filtered so I am breaking it up - apologies if you
get the original.]
 
CONTEXT: I was trying to verify a non-bindist installation by running the
testsuite on the target but neglected to match up the build gcc and
installation gcc leading to stange cc1 failures. (I can't use a bindist
distribution.)
 
I have now matched up the build and installation gcc and things are looking
up. For WAY=optc I get the following:
 
OVERALL SUMMARY for test run started at Sun Sep 11 18:45:07 BST 2011
    2612 total tests, which gave rise to
   14419 test cases, of which
       0 caused framework failures
   13106 were skipped
 
    1280 expected passes
      22 expected failures
       0 unexpected passes
      11 unexpected failures
 
Unexpected failures:
  4038(optc)
   Chan001(optc)
   MVar001(optc)
   QSem001(optc)
   QSemN001(optc)
   SampleVar001(optc)
   T3087(optc)
   cgrun025(optc)
   maessen_hashtab(optc)
   regex003(optc)
   space_leak_001(optc)
 
I think I am only approximating the build environment by using 2011.2.0.1.
Here is a breakdown in the failures.
 
*         5 of the tests (Chan-001-->SampleVar001) fail to find
Debug.QuickCheck
*         a further 3 static failures (T3087, maessen_hashtab & regex003)
*         cgrun025 bombs out with an irrefutable pattern failure
*         4038 fails to provide any output
*         I couldn't see what was wrong with space_leak_001
 
The testsuite appears to almost work standalone. Is it intended to? Or
should I place it in the source tree to test the installation?
 
Thanks!
 
Chris
 
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to