haskell / haskell/binary

How to test?

Open
#195 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Haskell
Stars
120
Forks
70
PR merge metrics
No merged PRs in 30d

Description

Are the build instructions in the README.md outdated? Using GHC-9.2.3 & cabal-install-3.6.2.0, I got package conflict errors at the `cabal configure --enable-tests --enable-benchmarks` on the git tag 0.8.9.0. The master branch yielded similar results. How can I test binary properly? `cabal build` works fine.
```
$ cabal configure --enable-tests --enable-benchmarks
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: binary-0.8.9.0 (user goal)
[__1] rejecting: binary:!bench (constraint from config file, command line
flag, or user target requires opposite flag selection)
[__1] trying: binary:*bench
[__2] trying: unordered-containers-0.2.19.1 (dependency of binary *bench)
[__3] trying: template-haskell-2.18.0.0/installed-2.18.0.0 (dependency of
unordered-containers)
[__4] trying: pretty-1.1.3.6/installed-1.1.3.6 (dependency of
template-haskell)
[__5] trying: hashable-1.4.0.2 (dependency of unordered-containers)
[__6] next goal: text (dependency of hashable)
[__6] rejecting: text-1.2.5.0/installed-1.2.5.0 (package is broken, missing
dependency binary-0.8.9.0)
[__6] rejecting: text-2.0, text-1.2.5.0 (cyclic dependencies; conflict set:
binary, hashable, text, unordered-containers)
[__6] rejecting: text-1.2.4.1 (conflict: template-haskell =>
base==4.16.2.0/installed-4.16.2.0, text => base>=4.3 && <4.16)
[__6] rejecting: text-1.2.4.0 (conflict: template-haskell =>
ghc-prim==0.8.0/installed-0.8.0, text => ghc-prim>=0.2 && <0.6)
[__6] rejecting: text-1.2.3.2 (conflict: template-haskell =>
base==4.16.2.0/installed-4.16.2.0, text => base>=4.14 && <4.15)
[__6] rejecting: text-1.2.3.1, text-1.2.3.0 (conflict: template-haskell =>
base==4.16.2.0/installed-4.16.2.0, text => base>=4.2 && <4.13)
[__6] rejecting: text-1.2.2.2 (conflict: hashable => text>=1.2.3.0 && <1.3 ||
>=2.0 && <2.1)
[__6] skipping: text-1.2.2.1, text-1.2.2.0, text-1.2.1.3, text-1.2.1.2,
text-1.2.1.1, text-1.2.1.0, text-1.2.0.6, text-1.2.0.5, text-1.2.0.4,
text-1.2.0.3, text-1.2.0.2, text-1.2.0.0, text-1.1.1.4, text-1.1.1.3,
text-1.1.1.2, text-1.1.1.1, text-1.1.1.0, text-1.1.0.1, text-1.1.0.0,
text-1.0.0.1, text-1.0.0.0, text-0.11.3.1, text-0.11.3.0, text-0.11.2.3,
text-0.11.2.2, text-0.11.2.1, text-0.11.2.0, text-0.11.1.13, text-0.11.1.12,
text-0.11.1.11, text-0.11.1.10, text-0.11.1.9, text-0.11.1.8, text-0.11.1.7,
text-0.11.1.6, text-0.11.1.5, text-0.11.1.3, text-0.11.1.2, text-0.11.1.1,
text-0.11.1.0, text-0.11.0.8, text-0.11.0.7, text-0.11.0.6, text-0.11.0.5,
text-0.11.0.4, text-0.11.0.3, text-0.11.0.2, text-0.11.0.1, text-0.11.0.0,
text-0.10.0.2, text-0.10.0.1, text-0.10.0.0, text-0.9.1.0, text-0.9.0.1,
text-0.9.0.0, text-0.8.1.0, text-0.8.0.0, text-0.7.2.1, text-0.7.1.0,
text-0.7.0.1, text-0.7, text-0.6, text-0.5, text-0.4, text-0.3, text-0.2,
text-0.1 (has the same characteristics that caused the previous version to
fail: excluded by constraint '>=1.2.3.0 && <1.3 || >=2.0 && <2.1' from
'hashable')
[__6] fail (backjumping, conflict set: binary, hashable, template-haskell,
text, unordered-containers)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: template-haskell, text, pretty,
generic-deriving, hashable, base, binary, unordered-containers, binary:bench
Try running with --minimize-conflict-set to improve the error message.
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with README.md and compare its build and test commands against the reported GHC-9.2.3 and cabal-install-3.6.2.0 behavior, especially `cabal configure --enable-tests --enable-benchmarks`. Done means the documented testing instructions work with supported tool versions, or clearly state the required versions and limitations.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
build-system, documentation, testing-qa
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.