1. 23 Nov, 2007 1 commit
  2. 06 Sep, 2007 1 commit
  3. 23 Aug, 2007 1 commit
  4. 27 Jun, 2007 1 commit
  5. 13 Apr, 2007 1 commit
  6. 05 Apr, 2007 1 commit
  7. 31 Mar, 2007 1 commit
  8. 21 Feb, 2007 1 commit
    • Simon Marlow's avatar
      Look for .T files in packages too · 55529322
      Simon Marlow authored
      This means we can put package-specific tests in the repository for the
      package, rather than putting them in the testsuite.  There should be a
      .T file to go with the tests, in the same way as for other tests in
      the testsuite (but this could be in addition to a standalone test
      driver that works with Cabal's 'setup test').
      55529322
  9. 06 Feb, 2007 1 commit
  10. 29 Aug, 2006 1 commit
    • Ian Lynagh's avatar
      Allow threading to be completely disabled with USETHREADS=0 · 33b3f651
      Ian Lynagh authored
      I had to pull the global classes and instances out into their own module
      as there was a catch-22: testlib needed to know if threading was enabled,
      but we don't know that until we have gone through the argument, but going
      through the arguments required changing things like config in testlib.
      33b3f651
  11. 22 Aug, 2006 1 commit
  12. 04 Feb, 2005 1 commit
  13. 19 Aug, 2003 1 commit
    • krc's avatar
      [project @ 2003-08-19 21:51:53 by krc] · a27b1e51
      krc authored
      Added support for testing generation and compilation of External Core
      code. There are two new ways, which are not automatically enabled but can be
      invoked from the command line: extcore and optextcore. Invoking either way will
      test that ghc is able to generate External Core code for a given test, read the
      code back in, and compile it to an executable that produces the expected output
      for the test.
      
      The External Core facility has a few limitations which result in certain tests
      failing for the "extcore" way.
        - External Core can't represent foreign calls other than static C calls
        - External Core can't correctly represent literals resulting from a
          "foreign label" declaration
        - External Core can't represent declarations of datatypes with no
          constructors
      The first of these was already known, and GHC panics if you tried to
      generate External Core for a program containing such a call. The second two
      cases were not handled properly before now; in another commit, I've changed the
      code that emits External Core to panic if either of them arises. Previously,
      GHC would happily generate External Core in either case, but would not be able
      to compile the resulting code.
      
      There are several tests that exhibit these limitations of External Core, so
      they've had to be made "expected failures" when compiling in the extcore or
      optextcore ways.
      a27b1e51
  14. 11 Sep, 2002 1 commit
    • simonmar's avatar
      [project @ 2002-09-11 10:47:57 by simonmar] · f2600f8b
      simonmar authored
      - Move some of the way-selection logic into the configuration file;
        the build system now just passes in variables saying whether the
        compiler supports profiling and native code generation, and the
        configuration file adds the appropriate ways.
      
      - Add a new option to the test driver, --way=<way> to select just a
        single way.
      f2600f8b
  15. 31 Jul, 2002 1 commit
    • simonmar's avatar
      [project @ 2002-07-31 14:24:18 by simonmar] · e5063a04
      simonmar authored
      Revamp the testsuite framework.  The previous framework was an
      experiment that got a little out of control - a whole new language
      with an interpreter written in Haskell was rather heavyweight and left
      us with a maintenance problem.
      
      So the new test driver is written in Python.  The downside is that you
      need Python to run the testsuite, but we don't think that's too big a
      problem since it only affects developers and Python installs pretty
      easily onto everything these days.
      
      Highlights:
      
        - 790 lines of Python, vs. 5300 lines of Haskell + 720 lines of
          <strange made-up language>.
      
        - the framework supports running tests in various "ways", which should
          catch more bugs.  By default, each test is run in three ways:
          normal, -O, and -O -fasm.  Additionally, if profiling libraries
          have been built, another way (-O -prof -auto-all) is added.  I plan
          to also add a 'GHCi' way.
      
          Running tests multiple ways has already shown up some new bugs!
      
        - documentation is in the README file and is somewhat improved.
      
        - the framework is rather less GHC-specific, and could without much
          difficulty be coaxed into using other compilers.  Most of the
          GHC-specificness is in a separate configuration file (config/ghc).
      
      Things may need a while to settle down.  Expect some unexpected
      failures.
      e5063a04