Transitive dependencies of benchmark suites not in Stackage

[RyanGlScott]

#1372 was closed, but there are still some issues with building benchmarks suites from Stackage, so I decided to open up a new issue.

In particular, I noticed in iu-parfunc/sc-haskell#7 that there are currently (as of LTS 5.17) some Stackage packages with benchmark suites whose dependencies are not on Stackage:

• cases-0.1.3 and ttrie-0.1.2.1 depend on criterion-plus
• cipher-aes-0.2.11, cipher-blowfish-0.0.3, cipher-camellia-0.0.2, cipher-des-0.0.6, and cipher-rc4-0.1.4 depend on crypto-cipher-benchmarks
• cmark-0.5.2 depends on discount and sundown
• stm-containers-0.2.10 depends on mwc-random-monad

Why doesn't Stackage include these packages?

[phadej]

Probably: https://github.com/fpco/stackage/blob/417fd34eac765ef8ca2248759371172676e43c76/build-constraints.yaml#L2871-L2881

[RyanGlScott]

Thanks @phadej, I didn't realize there were separate expected-benchmark-failures and skipped-benchmarks stanzas in build-constraints.yaml. It just sounds like I need to contact the maintainers about bumping their upper version bounds, then.

• For cmark: Restore cmark benchmarks #1458
• For stm-containers: Bump benchmark dependency upper bounds nikita-volkov/stm-containers#10
• For crypto-cipher-benchmarks: crypto-cipher-benchmarks: incompatible with newest criterion vincenthz/hs-crypto-cipher#46
• For criterion-plus: Out-of-date dependencies nikita-volkov/criterion-plus#2