GitLab

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').

Fixes the testsuite on Cygwin/MSYS using Cygwin Python.  I hope it
hasn't broken it using the native Python... if it has, we'll need to
revisit.  I can't see a good reason for the quotes, anyway.

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.

As well as being generally a good idea, os.access('foo') seems to return
true if foo.exe exists on Windows.

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.

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.

Before:
   tc056(normal)
   tc056(opt)
   tc056(optasm)
   tc056(prof)
   tc056(profasm)
   tc056(unreg)

After:
   tc056(normal,opt,optasm,prof,profasm,unreg)

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.

Infrastructure for testing Data structures.
 + some tests

tiny fix to simple_run(), adding a space between args and rts_flags.

interpter_run: add ">> return ()", to avoid GHCi trying to print
out (and evaluate) the result of Main.main.

Add skip_if_no_ghci

Disable the use of the timeout wrapper on Windows for now; it runs the
command using the wrong shell.