Skip to content

wasm-cross failures: Cabal complains about splitmix

Cabal finds itself unable to build a plan. But only sometimes. 🤔

Examples I've seen recently:

Log looks like

cabal error log
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: ghc-platform-0.1.0.0 (user goal)
[__1] trying: base-4.17.0.0/installed-4.17.0.0 (dependency of ghc-platform)
[__2] trying: hadrian-0.1.0.0 (user goal)
[__3] trying: hadrian:+selftest
[__4] trying: QuickCheck-2.14.2 (dependency of hadrian +selftest)
[__5] next goal: splitmix (dependency of QuickCheck)
[__5] rejecting: splitmix-0.1.0.4 (conflict:
base==4.17.0.0/installed-4.17.0.0, splitmix => base>=4.3 && <4.17)
[__5] skipping: splitmix-0.1.0.3, splitmix-0.1.0.2, splitmix-0.1.0.1,
splitmix-0.1, splitmix-0.0.5, splitmix-0.0.4, splitmix-0.0.3, splitmix-0.0.2,
splitmix-0.0.1, splitmix-0 (has the same characteristics that caused the
previous version to fail: excludes 'base' version 4.17.0.0)
[__5] fail (backjumping, conflict set: QuickCheck, base, splitmix)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: base, QuickCheck, splitmix, hadrian,
hadrian:selftest, ghc-platform

Giving it high priority because it keeps blocking Marge. This job is not run on the quick validate so doesn't get tested that often.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information