Re: validate on x86/MacOS

2007-07-16 Thread Ian Lynagh
On Mon, Jul 16, 2007 at 01:30:47PM +1000, Manuel M T Chakravarty wrote: > Ian Lynagh wrote, > >OK, I've made it get skipped in a fast testsuite run, so it won't cause > >problems with the validate script. So, I think that clears up the last > >issue with validate? > > Yes, at least on x86/MacOS ,

Re: validate on x86/MacOS

2007-07-15 Thread Manuel M T Chakravarty
Ian Lynagh wrote, OK, I've made it get skipped in a fast testsuite run, so it won't cause problems with the validate script. So, I think that clears up the last issue with validate? Yes, at least on x86/MacOS , today's tree passes validate! Are you going to announce it? Manuel __

Re: validate on x86/MacOS

2007-07-14 Thread Ian Lynagh
On Sat, Jul 14, 2007 at 08:04:41PM +0200, Pepe Iborra wrote: > > >break017 is strange - I was able to change the output merely by > > here btw) in a smaller test, with no luck. Sorry, but I've given up > for the moment. OK, I've made it get skipped in a fast testsuite run, so it won't cause

Re: validate on x86/MacOS

2007-07-14 Thread Pepe Iborra
On 13/07/2007, at 22:33, Simon Marlow wrote: Pepe Iborra wrote: I will be looking at them during today and tomorrow. print022 seems to be failing on some architectures but not in others, if I recall correctly, and for break017 I want to verify that the output is consistent among architect

Re: validate on x86/MacOS

2007-07-13 Thread Simon Marlow
. That leaves Ian capably holding the GHC fort. (Concerning the tests below, Ian you decide!) Simon | -Original Message- | From: Manuel M T Chakravarty [mailto:[EMAIL PROTECTED] | Sent: 12 July 2007 05:56 | To: Manuel M T Chakravarty; Simon Peyton-Jones; cvs-ghc@haskell.org | Subject: R

Re: validate on x86/MacOS

2007-07-12 Thread Manuel M T Chakravarty
: Manuel M T Chakravarty; Simon Peyton-Jones; cvs-ghc@haskell.org | Subject: Re: validate on x86/MacOS | | Ian Lynagh wrote, | > On Wed, Jul 11, 2007 at 08:54:28PM +1000, Manuel M T Chakravarty wrote: | >> I talked with SimonM on irc, and we managed to eliminate all | >> MacOS-sp

Re: validate on x86/MacOS

2007-07-12 Thread Pepe Iborra
Sent: 12 July 2007 05:56 | To: Manuel M T Chakravarty; Simon Peyton-Jones; cvs-ghc@haskell.org | Subject: Re: validate on x86/MacOS | | Ian Lynagh wrote, | > On Wed, Jul 11, 2007 at 08:54:28PM +1000, Manuel M T Chakravarty wrote: | >> I talked with SimonM on irc, and we managed to e

RE: validate on x86/MacOS

2007-07-12 Thread Simon Peyton-Jones
ly holding the GHC fort. (Concerning the tests below, Ian you decide!) Simon | -Original Message- | From: Manuel M T Chakravarty [mailto:[EMAIL PROTECTED] | Sent: 12 July 2007 05:56 | To: Manuel M T Chakravarty; Simon Peyton-Jones; cvs-ghc@haskell.org | Subject: Re: validate on x86/Mac

Re: validate on x86/MacOS

2007-07-11 Thread Manuel M T Chakravarty
Ian Lynagh wrote, On Wed, Jul 11, 2007 at 08:54:28PM +1000, Manuel M T Chakravarty wrote: I talked with SimonM on irc, and we managed to eliminate all MacOS-specific failures. What does that leave? Unexpected passes: print022(ghci) Unexpected failures: break017(ghci) Can you please

Re: validate on x86/MacOS

2007-07-11 Thread Ian Lynagh
On Wed, Jul 11, 2007 at 08:54:28PM +1000, Manuel M T Chakravarty wrote: > > I talked with SimonM on irc, and we managed to eliminate all > MacOS-specific failures. What does that leave? Can you please send the test outputs as well? Thanks Ian ___ C

Re: validate on x86/MacOS

2007-07-11 Thread Manuel M T Chakravarty
Simon Peyton-Jones wrote, I'll let Ian and/or Simon respond, since I don't have a recent build. The loop we are in right now is:> 1. reduce validate failures to zero 2. publish guidelines (requiring zero failures) I'm not sure we've completed (1) yet, so your qn is a good one.

RE: validate on x86/MacOS

2007-07-11 Thread Simon Peyton-Jones
I'll let Ian and/or Simon respond, since I don't have a recent build. The loop we are in right now is: 1. reduce validate failures to zero 2. publish guidelines (requiring zero failures) I'm not sure we've completed (1) yet, so your qn is a good one. S | -Original Message-