1. 16 Nov, 2011 1 commit
  2. 04 Nov, 2011 1 commit
  3. 08 Sep, 2011 1 commit
  4. 05 Sep, 2011 1 commit
  5. 20 Jul, 2011 1 commit
  6. 15 Jul, 2011 1 commit
  7. 17 Apr, 2011 1 commit
  8. 02 Apr, 2011 1 commit
  9. 02 Dec, 2010 1 commit
  10. 24 Sep, 2010 1 commit
  11. 18 Sep, 2010 1 commit
  12. 14 Sep, 2010 1 commit
  13. 13 Aug, 2010 2 commits
  14. 20 Oct, 2009 1 commit
  15. 08 Sep, 2009 1 commit
  16. 21 Aug, 2009 1 commit
  17. 25 Jun, 2009 1 commit
  18. 02 Jan, 2009 1 commit
  19. 11 Aug, 2008 1 commit
  20. 02 Apr, 2008 1 commit
  21. 09 May, 2007 1 commit
  22. 30 Mar, 2007 2 commits
  23. 15 Dec, 2006 1 commit
  24. 16 Nov, 2006 1 commit
  25. 12 Oct, 2006 1 commit
  26. 10 Apr, 2006 1 commit
  27. 31 Oct, 2005 1 commit
  28. 08 Jan, 2004 2 commits
  29. 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
  30. 11 Jul, 2001 1 commit
  31. 22 Jun, 2001 1 commit