You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you build tests with Cabal, the library they link to has a different package key than the library which is installed. I believe what's happening is that the full set of dependencies, including test dependencies, are being used to compute the key.
Here's a repro:
darcs clone http://hub.darcs.net/byorgey/split
cd split/
cabal sandbox init
cabal install
ghc-pkg field split key yields key: split_E4yadeCDng9EtdbI5MZoDg
When you build tests with Cabal, the library they link to has a different package key than the library which is installed. I believe what's happening is that the full set of dependencies, including test dependencies, are being used to compute the key.
Here's a repro:
ghc-pkg field split key
yieldskey: split_E4yadeCDng9EtdbI5MZoDg
grep key dist/dist-sandbox-ac80d1aa/package.conf.inplace/split-0.2.2-inplace.conf
yieldskey: split_E4yadeCDng9EtdbI5MZoDg
So far things are fine. However, if I do a
cabal install --enable-tests
:ghc-pkg field split key
yieldskey: split_E4yadeCDng9EtdbI5MZoDg
(same as before)grep key dist/dist-sandbox-ac80d1aa/package.conf.inplace/split-0.2.2-inplace.conf
yieldskey: split_IeGRGsZxCma0P7epq3xazi
(different!!!)This makes it extremely difficult to correctly merge HPC tix files from test-suites in different packages. See also https://ghc.haskell.org/trac/ghc/ticket/10952
The text was updated successfully, but these errors were encountered: