1. 28 Feb, 2007 1 commit
  2. 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
  3. 06 Feb, 2007 1 commit
  4. 02 Feb, 2007 1 commit
  5. 31 Jan, 2007 1 commit
  6. 16 Jan, 2007 1 commit
  7. 08 Jan, 2007 1 commit
  8. 05 Jan, 2007 1 commit
  9. 19 Dec, 2006 2 commits
  10. 15 Dec, 2006 2 commits
  11. 14 Dec, 2006 3 commits
  12. 09 Dec, 2006 1 commit
  13. 18 Sep, 2006 1 commit
  14. 25 Oct, 2006 1 commit
  15. 13 Oct, 2006 1 commit
  16. 17 Sep, 2006 1 commit
    • brianlsmith's avatar
      Allow testsuite to run under MSYS/MinGW using native Python (not Cygwin Python). · e1bdf63f
      brianlsmith authored
      This patch is based on a similar one "Enable timeout in Windows
      and don't require cygwin python" by Esa Ilari Vuokko. It seems
      like timeout is always built on Windows so I rearranged the logic
      there to make the code clearer, Esa's patch required the user to
      uncomment the MinGW-specific logic in order for it to work; this
      patch does not have the MinGW-specific logic commented out.
      
      I tested this on the trunk in Ubuntu 6.06 on i686 (VMWare).
      I tested this on the trunk and ghc-6.6 branch on Windows i686.
      e1bdf63f
  17. 10 Sep, 2006 2 commits
  18. 30 Aug, 2006 1 commit
  19. 29 Aug, 2006 2 commits
    • 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
    • Ian Lynagh's avatar
      Clean .hp files · a67606ed
      Ian Lynagh authored
      a67606ed
  20. 22 Aug, 2006 1 commit
  21. 13 Aug, 2006 1 commit
  22. 20 Mar, 2006 2 commits
    • Simon Marlow's avatar
      fix for GHCi tests that raise exceptions or exit · 2dbdcc36
      Simon Marlow authored
      We need to call GHC.TopHandler.runIOFastExit instead of
      GHC.TopHandler.runIO.  Recent fixes to the shutdown code have meant
      that when a thread invokes shutdownHaskellAndExit(), other main
      threads get a chance to exit (as they should), but this means that we
      might have a race between the child thread trying to exit the program
      and the main thread doing the same.  In the case of GHCi, if we're
      running an interpreted computation that needs to exit (as some tests
      do), then we really want this child thread to exit the program rather
      than the main thread.
      2dbdcc36
    • Simon Marlow's avatar
      sort the keys when outputting the summary · 0998d4fb
      Simon Marlow authored
      0998d4fb
  23. 16 Mar, 2006 2 commits
  24. 15 Mar, 2006 2 commits
  25. 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
  26. 26 Dec, 2005 1 commit
  27. 21 Oct, 2005 1 commit
  28. 23 May, 2005 1 commit
  29. 19 May, 2005 1 commit
  30. 11 Feb, 2005 1 commit
  31. 07 Feb, 2005 1 commit