1. 02 Jan, 2009 1 commit
  2. 31 Dec, 2008 1 commit
  3. 05 Dec, 2008 1 commit
  4. 11 Sep, 2008 1 commit
  5. 27 Aug, 2008 1 commit
  6. 26 Aug, 2008 1 commit
  7. 12 Aug, 2008 1 commit
  8. 11 Aug, 2008 2 commits
  9. 28 Jun, 2008 1 commit
  10. 16 Jun, 2008 1 commit
  11. 02 Apr, 2008 1 commit
  12. 21 Dec, 2007 1 commit
  13. 07 Dec, 2007 1 commit
  14. 11 Oct, 2007 1 commit
  15. 05 Oct, 2007 1 commit
  16. 29 Sep, 2007 1 commit
  17. 20 Sep, 2007 1 commit
  18. 24 Jun, 2007 1 commit
  19. 21 Jun, 2007 1 commit
  20. 09 May, 2007 1 commit
  21. 05 May, 2007 1 commit
  22. 30 Mar, 2007 2 commits
  23. 13 Jan, 2007 1 commit
  24. 03 Jan, 2007 1 commit
  25. 15 Dec, 2006 1 commit
  26. 24 Nov, 2006 1 commit
  27. 20 Nov, 2006 1 commit
  28. 16 Nov, 2006 1 commit
  29. 12 Oct, 2006 1 commit
  30. 28 Sep, 2006 1 commit
  31. 18 Aug, 2006 1 commit
  32. 12 Apr, 2006 1 commit
  33. 10 Apr, 2006 1 commit
  34. 18 Jan, 2006 1 commit
    • simonmar's avatar
      [project @ 2006-01-18 16:31:10 by simonmar] · ff6b4956
      simonmar authored
      Add a fast version of the testsuite
      
      The idea is to have a way to run as much of the testsuite as possible
      in a short time, so that we'll run it more often (such as just before
      checking in a change, for example).  'make fast' tries for good
      coverage without using too many cycles.  Currently it takes about 4
      minutes on a fast machine with an optimised GHC build; I think this
      might still be a little on the slow side.
      
      When you say 'make fast' in testsuite/tests/ghc-regress, we run each
      test only one way, and all of the long-running tests are omitted.
      Also, to get the runtime down further, I arbitrarily omitted many of
      the should_run tests (because these tend to take a lot longer than
      should_compile or should_fail tests).  I tried to keep a
      representative few in each category.
      ff6b4956
  35. 10 Nov, 2005 2 commits
  36. 31 Oct, 2005 1 commit
  37. 17 Oct, 2005 1 commit