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 architectures, and then accept it.
I'm pretty sure the output from these two tests (print022 and break017) varies
non-deterministically.
print022 was an expected fail before, and it was failing on several of the
nightly builds (and still is). It succeeds during most "validate" runs, though.
I suspect the difference is due to whether stage2 is compiled with
optimisation. Can you try a stage 2 with and without optimisation and see if
this happens for you?
break017 is strange - I was able to change the output merely by adding a comment
to the script. It might be related to print022, I guess.
Thanks for addinng tickets for the other failures. The result001 test I know
about; I don't think it's easy to fix, unfortunately.
Cheers,
Simon
Luckily I have Mac Os and Debian at hand, but buildbot will have to take
care of Windows & others.
Cheers
pepe
On 12/07/2007, at 9:47, Simon Peyton-Jones wrote:
Friends,
Simon M has gone to WG2.8, and will be away all next week too,
returning 23 July. I'm here till Friday, then away for 2 weeks
(WG2.8, then OSCON), returning 30 July. So that means that you won't
hear much from Simon+Simon for the next little while.
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; [email protected]
| 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-specific failures.
| >
| > What does that leave?
|
| Unexpected passes:
| print022(ghci)
|
| Unexpected failures:
| break017(ghci)
|
| > Can you please send the test outputs as well?
|
| print022
| ~~~~~~~~
| The test is marked as expect_broken in all.T. Test output
| is as in print022.stdout, as it unexpectedly passes. I am
| not sure why this is unexpected. It refers to bug #1457.
|
|
| break017
| ~~~~~~~~
| --- ./break017.stdout.normalised 2007-07-12
| 14:52:27.000000000 +1000
| +++ ./break017.run.stdout.normalised 2007-07-12
| 14:52:27.000000000 +1000
| @@ -4,6 +4,6 @@
| _result :: [a]
| a :: a
| as :: [a]
| -as = 'b' : 'c' : (_t1::[Char])
| *** Exception: Prelude.undefined
| -as = 'b' : 'c' : (_t2::[Char])
| +*** Exception: Prelude.undefined
| +as = 'b' : 'c' : (_t1::[Char])
| *** unexpected failure for break017(ghci)
|
| Maybe we we can just remove the expect_broken for print022
| and add an expect_broken for break017?
|
| Manuel
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
