More detail on breakage with ghc-6.10
All, We've been using the cabal-install build reporting stuff to get more detailed info on build failures with ghc-6.10 vs 6.8. cabal-install generates these build-reports.log files and individual log files for each build. Below is a list of packages that worked with 6.8 and fail with 6.10. If your package is on this list then you might like to take a look at the actual failure. I've posted the logs here: http://haskell.org/~duncan/ghc/hackage-failures-ghc-6.10/ There's one set for ghc-6.8 and one for 6.10. We can get quite a bit of info from these build-reports.log files just using grep, sort, uniq etc. However we also have a parser for it so we can write more interesting queries. For example, we're interested in regressions: reports68 <- fmap parseList (readFile "ghc-6.8/build-reports.log") reports610 <- fmap parseList (readFile "ghc-6.10/build-reports.log") let merged = mergeBy (comparing package) (sortBy (comparing package) reports68) (sortBy (comparing package) reports610) worked InstallOk = True worked _ = False failed InstallOk = False failed (DependencyFailed _) = False failed _ = True regressions = [ new | InBoth old new <- merged , worked (installOutcome old) && failed (installOutcome new) ] print (length regressions) mapM_ (putStrLn . display . package) regressions There are 58 in this list. Though some have been since fixed and it doesn't count packages that fail due to dependencies failing. Here's our current list. I've pruned a couple that I know have been fixed. ArrayRef-0.1.2 CLASE-2008.9.23.2 EdisonCore-1.2.1.2 HPDF-1.4 HTF-0.1 HaLeX-1.1 Hashell-0.15 Hipmunk-0.2 MemoTrie-0.0 NewBinary-0.1.1 OpenAFP-1.1 PArrows-0.1 TypeCompose-0.5 Vec-0.9.2 WebBits-0.9.2 YamlReference-0.9.2 Yampa-0.9.2.2 arrows-0.4 bytestring-show-0.2 cabal-setup-1.2.1 chp-1.1.0 cmath-0.3 fixpoint-0.1 frag-1.1.1 harpy-0.4 hasim-0.1 hask-home-2007.12.6 heap-0.4.0 hetris-0.2 hexpat-0.2 hinstaller-2008.2.16 hint-0.2.4.1 hslackbuilder-0.0.1 hsx-0.4.4 hxt-8.1.0 iException-0.0.1 libGenI-0.16.1 list-extras-0.2.2 logfloat-0.9.1 mage-1.1.0 numeric-prelude-0.0.4 parameterized-data-0.1.3 plugins-1.3 quantum-arrow-0.0.4 regex-tdfa-0.94 stream-fusion-0.1.1 streamproc-1.1 stringtable-atom-0.0.4 time-1.1.2.1 typalyze-0.1.1 unicode-prelude-0.1 utf8-light-0.3 xmonad-contrib-0.8 xmonad-utils-0.1 yhccore-0.9 Duncan
We've been using the cabal-install build reporting stuff to get more detailed info on build failures with ghc-6.10 vs 6.8. cabal-install generates these build-reports.log files and individual log files for each build.
Since you do have the infrastructure set up: haddock is also changing with ghc-6.10. Are the no (visible) issues resulting from that (which would be great!), or didn't your tests include haddocking? Claus
claus.reinke:
We've been using the cabal-install build reporting stuff to get more detailed info on build failures with ghc-6.10 vs 6.8. cabal-install generates these build-reports.log files and individual log files for each build.
Since you do have the infrastructure set up: haddock is also changing with ghc-6.10. Are the no (visible) issues resulting from that (which would be great!), or didn't your tests include haddocking?
No haddock tests yet, but we can start doing that. Good idea.
Am Samstag, 11. Oktober 2008 09:36 schrieb Duncan Coutts:
All,
We've been using the cabal-install build reporting stuff to get more detailed info on build failures with ghc-6.10 vs 6.8. cabal-install generates these build-reports.log files and individual log files for each build.
build-reports.log informs me that configure failed for the lax package with both GHC 6.8 and GHC 6.10. However, lax used to build fine on my machine with GHC 6.8. So I looked at logs/lax-0.0.0.1.log but this file is empty. Why? Best wishes, Wolfgang
Am Donnerstag, 23. Oktober 2008 12:59 schrieb Wolfgang Jeltsch:
Am Samstag, 11. Oktober 2008 09:36 schrieb Duncan Coutts:
All,
We've been using the cabal-install build reporting stuff to get more detailed info on build failures with ghc-6.10 vs 6.8. cabal-install generates these build-reports.log files and individual log files for each build.
build-reports.log informs me that configure failed for the lax package with both GHC 6.8 and GHC 6.10. However, lax used to build fine on my machine with GHC 6.8. So I looked at logs/lax-0.0.0.1.log but this file is empty. Why?
Best wishes, Wolfgang
lax-0.0.0.1 just built fine for me using 6.8.3, package: lax-0.0.0.1 os: linux arch: i386 compiler: ghc-6.8.3 client: cabal-install-0.6.0 flags: dependencies: base-3.0.2.0 install-outcome: InstallOk docs-outcome: NotTried tests-outcome: NotTried Probably the log is empty because no build outcomes have been reported (I just tried cabal report and got cabal: /home/dafis/.cabal/reports/hackage.haskell.org: getDirectoryContents: does not exist (No such file or directory) , I can't be bothered now to find out what I'd have to do to make it work). Cheers, Daniel
g9ks157k:
Am Samstag, 11. Oktober 2008 09:36 schrieb Duncan Coutts:
All,
We've been using the cabal-install build reporting stuff to get more detailed info on build failures with ghc-6.10 vs 6.8. cabal-install generates these build-reports.log files and individual log files for each build.
build-reports.log informs me that configure failed for the lax package with both GHC 6.8 and GHC 6.10. However, lax used to build fine on my machine with GHC 6.8. So I looked at logs/lax-0.0.0.1.log but this file is empty. Why?
Resolving dependencies... 'lax-0.0.0.1' is cached. cabal: The package requires Cabal library version -any && >=1.2 && <1.4 but no suitable version is installed. cabal: Error: some packages failed to install Perhaps?
On Thu, 2008-10-23 at 12:59 +0200, Wolfgang Jeltsch wrote:
Am Samstag, 11. Oktober 2008 09:36 schrieb Duncan Coutts:
All,
We've been using the cabal-install build reporting stuff to get more detailed info on build failures with ghc-6.10 vs 6.8. cabal-install generates these build-reports.log files and individual log files for each build.
build-reports.log informs me that configure failed for the lax package with both GHC 6.8 and GHC 6.10. However, lax used to build fine on my machine with GHC 6.8. So I looked at logs/lax-0.0.0.1.log but this file is empty. Why?
As Don noted, it's because it didn't even get to the stage of running the configure for the package. That's the first part where it starts logging. Yes, the logging is sadly rather primitive. Duncan
participants (5)
-
Claus Reinke -
Daniel Fischer -
Don Stewart -
Duncan Coutts -
Wolfgang Jeltsch