From dd12fe3802c0b2125249ac3eb4a1610726300be1 Mon Sep 17 00:00:00 2001 From: Mihai Maruseac Date: Sat, 27 May 2017 08:55:23 -0700 Subject: [PATCH] Disable cryptohash-* benchmarks, #2538 (comment-304458844) --- build-constraints.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/build-constraints.yaml b/build-constraints.yaml index 2f3e14a5..15424237 100644 --- a/build-constraints.yaml +++ b/build-constraints.yaml @@ -3721,6 +3721,12 @@ skipped-benchmarks: # Cyclic dependencies - cassava + # Won't be updated only for the benchmark component + # (https://github.com/fpco/stackage/issues/2538#issuecomment-304458844) + - cryptohash-md5 + - cryptohash-sha1 + - cryptohash-sha256 + # end of skipped-benchmarks @@ -3844,6 +3850,9 @@ tell-me-when-its-released: - req-0.2.0 # Remove from expected-test-failures https://github.com/mrkkrp/req/issues/14#issuecomment-287562784 - vivid-0.2.0.5 # Re-enable package (disabed per MonadRandom < 0.5) https://github.com/fpco/stackage/issues/2180 - lens-4.15.2 # Test failures in lens-4.15.1 https://github.com/fpco/stackage/issues/2496 +- cryptohash-md5-0.11.100.1 # re-enable benchmarks, https://github.com/fpco/stackage/issues/2538#issuecomment-304458844 +- cryptohash-sha1-0.11.100.1 # re-enable benchmarks, https://github.com/fpco/stackage/issues/2538#issuecomment-304458844 +- cryptohash-sha256-0.11.100.1 # re-enable benchmarks, https://github.com/fpco/stackage/issues/2538#issuecomment-304458844 # Packages which should be hidden after registering, to avoid module name # conflicts. This is intended for at least two use cases: