on master help sign in
Re-enable expected benchmark failures to find out why they are disabled...
commit54a809c2ea10f8dcf879858b6ec486a282de06d8 authorAdam Bergmark <adam@bergmark.nl> dateSun 28 Aug 2016, 23:33 (10 years ago) parentbbb42d8
1 file changed+5−22
build-constraints.yaml+5−22
build-constraints.yaml+5−22
@@ -2835,35 +2835,18 @@ expected-test-failures:
28352835# Benchmarks which are known not to build. Note that, currently we do not run
28362836# benchmarks, and therefore failures are only for building, not running.
28372837expected-benchmark-failures:
2838− - Frames
2839− - attoparsec
2840− - cipher-aes128
2841− - cryptohash
2842− - dbus
2843− - hashable
2844− - http-link-header
2845− - jose-jwt
2846− - lens
2847− - lucid
2848− - picoparsec
2849− - thyme
2850− - web-routing
2851− - xmlgen
2852− - yi-rope
2853−
28542838 # https://github.com/commercialhaskell/stack/issues/2153
28552839 - scientific
28562840 - vector-binary-instances
28572841
2858− # GHC 8
2859− - cassava
2842+ # Missing files in sdist
2843+ - cassava # https://github.com/hvr/cassava/pull/117
28602844
28612845 # Recursive deps https://github.com/fpco/stackage/issues/1818
2862− # 0.2.7.1 unordered-containers:bench -> criterion:lib -> aeson:lib -> unordered-containers:lib
2863− - unordered-containers
2846+ - unordered-containers # 0.2.7.1 unordered-containers:bench -> criterion:lib -> aeson:lib -> unordered-containers:lib
28642847
2865− # 0.3.2, Because of stackage upper bound
2866− - cassava-conduit
2848+ # Stackage upper bounds, re-enable these when their upper bound is removed
2849+ - cassava-conduit # 0.3.2
28672850
28682851# end of expected-benchmark-failures
28692852