patch applied (ghc): Add assertion for arity match (checks Trac
marlowsd at gmail.com
Tue Dec 16 04:09:54 EST 2008
Thomas Schilling wrote:
> My validate always has process008 failing (missing printf). The rest is fine.
And ironically, in the logs we find:
Thu Oct 2 00:23:39 GMT Daylight Time 2008 Ian Lynagh <igloo at earth.li>
* Use printf rather than echo for the process008 test
It doesn't work on Windows for me otherwise
It works for me with echo (on Cygwin). Ian - what's the problem here?
Presumably MSYS doesn't come with printf by default, so we need to fix this.
> 2008/12/10 Simon Marlow <marlowsd at gmail.com>:
>> Simon Marlow wrote:
>>> Simon Peyton-Jones wrote:
>>>> | Hooray for the testsuite and validate: out of 2000+ tests, there was
>>>> | exactly 1 (ONE) that demonstrated this bug, and it was in a test for
>>>> | System.Random library of all things. This serves as a reminder to all
>>>> | us: any test failure should be treated as suspicious, even if it
>>>> | look at all related to something you changed, and this is exactly why
>>>> | have to keep validate clean. I am now a fully paid-up validate
>>>> On Windows (MSYS) I get several failures that I'm pretty sure have been
>>>> there for a while. They seem to relate to things like 'printf' not
>>>> existing. That makes it harder to interpret a Windows validate run.
>>>> I wonder if someone (Neil? Ian?) might investigate?
>>> I see some, but not all of those failures on our buildbots, I'll
>>> investigate. We had zero failures a few days ago, so I think these are new.
>> Well, on closer inspection we currently have zero failures on the Cygwin
>> buildbots, for the fast/validate testsuite. I don't have an MSYS build set
>> up, so could someone else try with that?
>> Cvs-ghc mailing list
>> Cvs-ghc at haskell.org
More information about the Cvs-ghc