RE: Validate test failures

2012-06-25 Thread Simon Peyton-Jones
I failed to push some patches; now done S | -Original Message- | From: cvs-ghc-boun...@haskell.org [mailto:cvs-ghc-boun...@haskell.org] | On Behalf Of Ian Lynagh | Sent: 23 June 2012 14:19 | To: cvs-ghc@haskell.org | Subject: Validate test failures | | | Hi all, | | There are

Validate test failures

2012-06-23 Thread Ian Lynagh
Hi all, There are currently 3 test failures when validating: typecheck/should_compile T4361 [exit code non-0] (normal) typecheck/should_fail tcfail181 [stderr mismatch] (normal) typecheck/should_fail tcfail189 [stderr mismatch] (normal) Does anyone know what's going on?

Re: validate test failures

2011-08-10 Thread David Terei
On 10 August 2011 03:18, Manuel M T Chakravarty wrote: > So, now we are down to two failures: > >> Unexpected failures: >>    cabal                  ghcpkg01 [bad stdout] (normal) >>    concurrent/should_run  numsparks001 [bad exit code] (threaded1) > > For ghcpkg01, I get > Oops! Thanks, this is

Re: validate test failures

2011-08-10 Thread Manuel M T Chakravarty
Simon Peyton-Jones: > This is Duncan. He's working on it; to quote: > > | Mm. > | > | I'll see what my extra tracing turns up. I may not have time to look at > | this today. I've got a couple deadlines today. > > Maybe turn to expect_broken to avoid discombobulation? It sounds as if he wil

RE: validate test failures

2011-08-10 Thread Simon Peyton-Jones
| > Stderr: | > numsparks001: internal error: ASSERTION FAILED: file rts/Schedule.c, line 1473 | > | > (GHC version 7.3.20110809 for x86_64_apple_darwin) | > Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug | > | > *** unexpected failure for numsparks001(threaded1) |

Re: validate test failures

2011-08-10 Thread Manuel M T Chakravarty
So, now we are down to two failures: > Unexpected failures: >cabal ghcpkg01 [bad stdout] (normal) >concurrent/should_run numsparks001 [bad exit code] (threaded1) For ghcpkg01, I get > Actual stdout output differs from expected: > --- ./cabal/ghcpkg01.stdout 2011-07-27

Re: validate test failures

2011-08-10 Thread Manuel M T Chakravarty
David Terei: > The Safe Haskell ones have been fixed a couple of hours back, if you > pull the latest testsuite but are getting failure let me know. One of my repos somehow forgot which remote it was tracking, which stopped ./sync-all prematurely — so, it didn't pull all repos. Sorry, Manuel >

Re: validate test failures

2011-08-10 Thread David Terei
The Safe Haskell ones have been fixed a couple of hours back, if you pull the latest testsuite but are getting failure let me know. Cheers, David On 9 August 2011 22:03, Manuel M T Chakravarty wrote: > A few days ago, I had zero failures on OS X, now I have > >> Unexpected passes: >>    th/TH_re

validate test failures

2011-08-09 Thread Manuel M T Chakravarty
A few days ago, I had zero failures on OS X, now I have > Unexpected passes: >th/TH_recompile TH_recompile (normal) > > Unexpected failures: >cabalghcpkg01 [bad stdout] (normal) >ghci/scripts T4127 [bad stdout] (ghci) >module mod9