1. 12 Oct, 2004 1 commit
  2. 09 Sep, 2004 1 commit
  3. 06 Sep, 2004 2 commits
  4. 01 Sep, 2004 1 commit
  5. 19 Jul, 2004 1 commit
    • igloo's avatar
      [project @ 2004-07-19 22:11:45 by igloo] · 805e7047
      igloo authored
      Allows a -ws-64 stdout variant rather than requiring each 64-bit
      platform to have a -platform one. (You now need to make boot in
      testsuite after configure but before running tests).
      
      Modify enum001, partly to alter spacing but also to inline printTest
      where things like \NUL are used, as modern cpp behaves differently.
      
      Rename the generated .script files to .genscript to make it easier to
      clean a testsuite tree.
      805e7047
  6. 16 Mar, 2004 1 commit
  7. 17 Feb, 2004 1 commit
  8. 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
  9. 25 Jul, 2003 1 commit
  10. 23 Jul, 2003 3 commits
    • simonmar's avatar
      [project @ 2003-07-23 11:39:31 by simonmar] · 6c2bb842
      simonmar authored
      ghci_script:
        - filter out -no-recomp from the compiler flags (we want to
          test recompilation)
        - pass config.compiler and config.compiler_always_flags to the
          subprocess via the environment variables HC and HC_OPTS
          respectively, so that the GHCi script can invoke the compiler
      6c2bb842
    • simonmar's avatar
      [project @ 2003-07-23 09:54:09 by simonmar] · 8cb98436
      simonmar authored
      Add ghci_script, a simple variation on run_command that runs GHCi with
      a specified script as input.
      8cb98436
    • simonmar's avatar
      [project @ 2003-07-23 09:22:29 by simonmar] · ecb2cccb
      simonmar authored
      Extend the support for running arbitrary commands as tests.
      
      - generic_command is now called run_command
      
      - the stdin for the command can be redirected in the same way as for a
        normal test.
      
      - the command's stdout and stderr outputs are compared against
        <testname>.stdout and <testname>.stderr as for a normal test
      
      - running a command and ignoring the output altogether (just the
        exit code is checked) is provided by calling
        run_command_ignore_output instead of run_command.
      ecb2cccb
  11. 22 Jul, 2003 1 commit
  12. 17 Jul, 2003 1 commit
  13. 26 Mar, 2003 1 commit
  14. 10 Dec, 2002 1 commit
  15. 02 Dec, 2002 4 commits
  16. 20 Aug, 2002 1 commit
  17. 01 Aug, 2002 2 commits
  18. 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