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