Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Get tests working with MicroHs

Open
#1,120 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell

Research direction

Start with the set-properties test suite and the provided cabal-plan topo output to identify which dependencies are not compatible with MicroHs. Determine the compatibility work needed for the non-GHC-only dependencies, then verify that the tests run successfully with MicroHs.

Written by the indexing model from the issue text.

Description

testing

Now that we can build with MicroHs, we should try to get tests working too.

Output of cabal-plan topo on set-properties with GHC 9.12.1, cabal 3.14.1.1:

containers-tests-0 test:set-properties
tasty-quickcheck-0.11.1
tasty-hunit-0.10.2
tasty-1.5.3
tagged-0.8.9
optparse-applicative-0.18.1.0
transformers-compat-0.7.2
process-1.6.25.0
directory-1.3.9.0
file-io-0.1.5
unix-2.8.6.0
time-1.14
filepath-1.5.4.0
os-string-2.0.7
exceptions-0.10.9
stm-2.5.3.1
prettyprinter-ansi-terminal-1.1.3
prettyprinter-1.7.1
text-2.1.2
containers-tests-0
call-stack-0.4.0
binary-0.8.9.2
ansi-terminal-1.1.2
ansi-terminal-types-1.1
colour-2.3.6
QuickCheck-2.15.0.1
random-1.2.1.3
splitmix-0.1.1
mtl-2.3.1
transformers-0.6.1.2
bytestring-0.12.2.0
containers-0.7
template-haskell-2.23.0.0
ghc-boot-th-9.12.1
pretty-1.1.3.6
deepseq-1.5.1.0
array-0.5.8.0
base-4.21.0.0
ghc-internal-9.1201.0
ghc-bignum-1.3
ghc-prim-0.13.0
rts-1.0.2

Some of these are GHC only, but the rest will need to be made compatible with MicroHs.

Not sure how feasible/time-consuming that will be, just putting this up for now.

Dominant language
Haskell
Stars
356
Forks
196
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from haskell/containers

All issues in haskell/containers

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.