ghci and other test failures on Windows.

[Simon Marlow]

On 04 September 2004 10:50, Mike Thomas wrote:

> Hi Simon.
> 
>  > > 3.  The next step after fixing the test script issue for point 1
>  for > > the Windows regression tests will need to be the Windows
>  compiler > > crashes and network hangs reported a while ago - no
>  promises of > > course - the problems I expect are long standing.
> 
>  > These must have dropped off my radar - can you remind me?
> 
> I just tabulated the first twenty or so ghc compiler crashes as the
> test suite ran this evening (all of them writes to invalid locations)
> on stable branch up to date as of about midday:
> 
> finalization001.hs
> hClose001.hs
> hFileSize001(ghci)
> hFlush001(ghci)
> hGetLine001(ghci)
> hGetPosn001(ghci)
> hIsEOF002(ghci)
> hReady001(ghci)
> hSeek001(ghci)
> hSeek002(ghci)
> hSeek003(ghci)
> hSeek004(ghci)
> hSetBuffering002(ghci)
> ioeGetErrorString001(ghci)
> ioeGetFileName001(ghci)
> ioeGetHandle001(ghci)
> misc001(ghci)
> openFile001(ghci)
> openFile004(ghci)
> openFile005(ghci)
> openFile007(ghci)
> readFile001(ghci)

I just ran the testsuite in lib/IO with an up to date STABLE build on
Windows, and I don't see the crashes you reported.  I do get several
failures - I've updated the sample output and fixed the test driver in a
couple of places.  

There are some real failures in lib/IO due to the fact that Windows
doesn't implement Handle locking, probably these should be marked known
failures for the release.

Cheers,
	Simon