GitLab

os.spawnv is broken on non-cygwin Windows (looks like it goes via a shell).

The user001 test in the unix package can fail when stdin comes from a
file.

Fixes some framework failures.

When working on a new foo extension, you can now put your tests in the
testsuite, set ProjectTags=-foo in mk/build.mk and skip_unless_tag('foo')
in the tests.

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.