Thorkil: Thanks for the diligent tracking.
Claus: any suggestions in how to reproduce this would be welcome.
As I mentioned earlier, I wasn't able to reproduce it myself,
though I only tried starting from patches mentioning QA.hs or
Check.hs. The actual error pattern is familiar, though, and has
Hi Tim
Sounds a great idea. My only question is the name for the library -
ext-core in the GHC tree means implicitly GHC, and the library name
means external core. On hackage ghc-core would implicitly mean
external, and the name means GHC Core. Just a thought, and doesn't
matter too much - I'd use
On Fri, Sep 12, 2008 at 11:07:18PM -0700, Tim Chevalier wrote:
>
> -rwx-- 1 root root 134 2008-09-12 22:28 ghc-6.9.20080912
Thanks for the report; I've fixed it locally and will push once I've
validated etc.
Thanks
Ian
___
Cvs-ghc mailing list
Eric Kow <[EMAIL PROTECTED]> added the comment:
Thorkil: Thanks for the diligent tracking.
Claus: any suggestions in how to reproduce this would be welcome.
Reading your past comment more carefully, I noticed this
> it is just possible that the Cabal repo I pulled into already had
> leftover st
Thorkil Naur <[EMAIL PROTECTED]> added the comment:
I have tried this, but unfortunately, I have not been able to reproduce the
problem. Some details follow.
Starting at repository Cabal-0, a version of the libraries/Cabal repository with
> thorkil-naurs-mac-mini:~/tn/test/darcs/Issue/1034/wor
Build results:
x86-64 Linux head:fail (failed stage1) fail (failed stage1)
x86 Windows head: fail (failed nofib.boot.0 nofib.boot.0_2
nofib.boot.0_3 nofib.boot.0_4 nofib.boot.0_5)
x86 Windows head fast:fail (failed getsubrepos) pass fail (failed
getsubrepos) fail (
Build results:
tnaur PPC OSX stable 2: pass
tnaur x86 Linux stable: pass
x86 Windows stable: fail (failed stage1)
x86 Windows stable fast: lost pass pass fail (failed stage1) pass
x86-64 Linux stable: fail (failed stage1)
Old unexpected test failures:
TyFamUndec 4 gabor s
