Re-enable expected benchmark failures to find out why they are disabled...

build-constraints.yaml

@@ -2835,35 +2835,18 @@ expected-test-failures:
 # Benchmarks which are known not to build. Note that, currently we do not run
 # benchmarks, and therefore failures are only for building, not running.
 expected-benchmark-failures:
-    - Frames
-    - attoparsec
-    - cipher-aes128
-    - cryptohash
-    - dbus
-    - hashable
-    - http-link-header
-    - jose-jwt
-    - lens
-    - lucid
-    - picoparsec
-    - thyme
-    - web-routing
-    - xmlgen
-    - yi-rope
-
     # https://github.com/commercialhaskell/stack/issues/2153
     - scientific
     - vector-binary-instances
 
-    # GHC 8
+    # Missing files in sdist
-    - cassava
+    - cassava # https://github.com/hvr/cassava/pull/117
 
     # Recursive deps https://github.com/fpco/stackage/issues/1818
-    # 0.2.7.1 unordered-containers:bench -> criterion:lib -> aeson:lib -> unordered-containers:lib
+    - unordered-containers # 0.2.7.1 unordered-containers:bench -> criterion:lib -> aeson:lib -> unordered-containers:lib
-    - unordered-containers
 
-    # 0.3.2, Because of stackage upper bound
+    # Stackage upper bounds, re-enable these when their upper bound is removed
-    - cassava-conduit
+    - cassava-conduit # 0.3.2
 
 # end of expected-benchmark-failures