Test Suite's Dependency on Quickcheck

If you build GHC with just the default settings, QuickCheck doesn't get pulled from Darcs and it is thus not built and installed into ghc-inplace. Because of this, many of the tests in the test suite fail: SampleVar001 Chan001 MVar001 QSemN001 QSem001 bytestring001 bytestring004 bytestring005 I think that the test suite should run without errors by default. What is the best way to deal with this situation? Probably the easiest thing to do would be to include QuickCheck as a "core package" as defined in the thread "Packages in GHC 6.6." Then QuickCheck would need to be copied into the ghc-6.6 branch. Thoughts? - Brian

After further review, I can see that the test suite also requires 'network,' 'html,' and 'mtl' for all the tests to pass. Maybe we need to separate the packages into three groups: core, tests, and extras, where all the packages required by the test suite would get put into the "tests" group? Besides the dependencies on these non-core packages, there are 7 tests (maybe a couple more) that only work on Cygwin or Unix, but fail on MSYS/MinGW. Would you accept patches to these tests to make them run without Cygwin on Windows? The tests that would need to be patched are: * cabal01 and cabal02 Cabal is trying to execute ghc\compiler\stage2\ghc-inplace which is a shell script. Cabal expects it to be an executable. * process001, process002, and process003 These tests have "c:/cygwin/bin/ls" hard-coded into them, so they will fail on any system that doesn't have Cygwin in that exact location. * prog001, prog002, and prog003 These tests execute Unix commands like "rm," and "ls" via :shell, so they fail on non-Unix/non-Cygwin systems. Tests requiring package 'QuickCheck': =====> SampleVar001 =====> Chan001 =====> MVar001 =====> QSemN001 =====> QSem001 =====> bytestring001 =====> bytestring004 =====> bytestring005 =====> ghci014 =====> maessen_hashtab Tests requiring package 'mtl': =====> mod133 =====> drvfail006 =====> drvfail008 =====> reify =====> tc183 =====> tcfail126 =====> tree Tests requiring package 'network' (and, transitively, package 'html'): =====> net001 =====> net002 =====> conc056 =====> pkg02_b =====> uri001 On 9/12/06, Brian Smith < brianlsmith@gmail.com> wrote:
If you build GHC with just the default settings, QuickCheck doesn't get pulled from Darcs and it is thus not built and installed into ghc-inplace. Because of this, many of the tests in the test suite fail:
SampleVar001 Chan001 MVar001 QSemN001 QSem001 bytestring001 bytestring004 bytestring005
I think that the test suite should run without errors by default. What is the best way to deal with this situation? Probably the easiest thing to do would be to include QuickCheck as a "core package" as defined in the thread "Packages in GHC 6.6." Then QuickCheck would need to be copied into the ghc-6.6 branch. Thoughts?
- Brian

Hello Brian, Wednesday, September 13, 2006, 10:17:10 AM, you wrote:
Maybe we need to separate the packages into three groups: core, tests, and extras, where all the packages required by the test suite would get put into the "tests" group?
or core, ghc-for-ghc and don't-matter? :) -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com

On Wed, 2006-09-13 at 01:17 -0500, Brian Smith wrote:
After further review, I can see that the test suite also requires 'network,' 'html,' and 'mtl' for all the tests to pass.
Maybe we need to separate the packages into three groups: core, tests, and extras, where all the packages required by the test suite would get put into the "tests" group?
I would suggest a better approach is to simply have the testsuite be more of an independent package and just accept that it depends on ghc and the other packages. This what we're doing in gentoo now, we have a 'pseudo' package "ghc-testsuite" that depends on ghc, mtl, quickcheck etc. (It's 'pseudo' in the sense that it doesn't install anything except the testsuite summary results). The testsuite has a few assumptions that it's located inside a configured ghc build tree. If this could be made simpler then this would seem a sensible approach. Duncan
participants (3)
-
Brian Smith
-
Bulat Ziganshin
-
Duncan Coutts