Hi
> > Could it be that buffering has a different default on Windows? > > 2228 is now an expected failure on Windows. See #2628. Fair enough. > > As a secondary issue, it appears that the failure reports > are occuring > > after the script has started to print out information about > the next > > test. > > That's probably because the testsuite is running in parallel, > which it does automatically when validating if you have a new > enough version of Python. That sounds reasonable. Perhaps on writing an error message to the log, the script could always write out "*** unexpected failure for break008(ghci)" both _before_ and after the test fail report - so its immediately clear which test is failing. Then again, I think it's the kind of thing that will only confuse someone once :-) Thanks Neil ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== _______________________________________________ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
