Re: Windows faliures

2010-01-29 Thread Andrew Suffield
On Fri, Jan 29, 2010 at 09:30:38AM +, Simon Marlow wrote: > The openTempFile001 failure is probably harmless, it just indicates > that we tried to write a character that isn't known in your current > locale (maybe you can set your locale to a Unicode one, I can't > remember how to do that on Wi

Re: Windows faliures

2010-01-29 Thread Simon Marlow
On 29/01/10 00:15, Simon Peyton-Jones wrote: On Windows I’m getting these failures Simon Unexpected failures: ThreadDelay001(normal) cgrun017(normal) cgrun032(normal) hsc2hs001(normal) hsc2hs002(normal) openTempFile001(normal) Strange - I did a Windows validate yesterday and got zero failure

Windows faliures

2010-01-28 Thread Simon Peyton-Jones
On Windows I'm getting these failures Simon Unexpected failures: ThreadDelay001(normal) cgrun017(normal) cgrun032(normal) hsc2hs001(normal) hsc2hs002(normal) openTempFile001(normal) => hsc2hs001(normal) 823 of 2434 [0, 2, 0] cd ./hsc2hs && $MAKE -s --no-print-directory hsc