ANNOUNCE: GHC 7.10.2 Release Candidate 2

[Edward Z. Yang]

T10279 and sigcabal01 should be harmless; if you want to make the
testsuite stop bleating about them you can mark them as failing but
please open a bug so we can eventually fix it.  I'm currently on
vacation and cannot immediately offer fixes.

(T10279 ought to work on Mac but I guess something platform specific is
poking a non-failable lookup too early so we don't get to give a good
error message.  Hard to debug without a Mac.)

Edward

Excerpts from Richard Eisenberg's message of 2015-07-03 19:26:17 -0700:
> Fixes for the T10019 and T10534 issues are in D1036.
> 
> Edward Y, the issue around T10279 looks like your territory...
> 
> And the first four have been failing for me on Mac for a long time (months, at least). I don't know anything about them.
> 
> Richard
> 
> On Jul 3, 2015, at 7:28 PM, Mark Lentczner <mark.lentczner at gmail.com> wrote:
> 
> > OS X GHC build has these test failures:
> > 
> > Unexpected failures:
> >    cabal/sigcabal01       sigcabal01 [bad stderr] (normal)
> >    driver/retc001         retc001 [bad stderr] (normal)
> >    ffi/should_run         T2276_ghci [bad exit code] (ghci)
> >    rts                    linker_unload [bad exit code] (normal)
> >    th                     T10019 [bad stdout] (ghci)
> >    th                     T10279 [stderr mismatch] (normal)
> >    typecheck/should_fail  T10534 [stderr mismatch] (normal)
> > 
> > sigcabal01 looks like tests that depend on generated names or offsets that are just different under OS X
> > 
> > retc001 - test looks busted to me: Does GHC now exit with a process error code of non-zero when compilation fails? If so, the Makefile needs fixing.
> > 
> > T2276_ghci - looks like -Wignored-attributes broke this test?
> > 
> > linker_unload - malloc.h is in malloc/malloc.h under OS X (!)
> > 
> > T10019 - magic generated symbol in "golden" test out is wrong: 'a_1627391544' vs. 'a_1627391540'
> > 
> > T10279 - panic! (the 'impossible' happened) gual_pkg rts-1.0
> > 
> > T10534 - text message punctation change
> > 
> > There were also a bunch of performance deviations - but they were mostly just out of bounds or wildly different (over by 100%.... under by 50%!)
> > 
> > 
> > _______________________________________________
> > ghc-devs mailing list
> > ghc-devs at haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs