From ae4c8919aecde1d3636d98ac02f28b6c3d8cd364 Mon Sep 17 00:00:00 2001
From: Michael Snoyman <michael@snoyman.com>
Date: Thu, 16 Feb 2017 08:47:38 +0200
Subject: [PATCH] Add back stackage-curator (store-0.3.1 fixes memory issues)

Skips benchmark due to criterion, and adds store explicitly
---
 build-constraints.yaml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/build-constraints.yaml b/build-constraints.yaml
index 1c7012ab..385cbd2d 100644
--- a/build-constraints.yaml
+++ b/build-constraints.yaml
@@ -121,7 +121,8 @@ packages:
         - persistent-postgresql
         - persistent-sqlite
         - persistent-template
-        # - stackage-curator # via store https://github.com/fpco/stackage/issues/2283
+        - stackage-curator
+        - store
         - stm-conduit
         - wai-websockets
         - warp-tls
@@ -3046,6 +3047,9 @@ skipped-tests:
     # via criterion: via cassava: bounds: vector
     - sparse-linear-algebra
 
+    # criterion
+    - store
+
 # end of skipped-tests
 
 # Tests which we should build and run, but which are expected to fail. We
@@ -3462,8 +3466,10 @@ skipped-benchmarks:
     - sourcemap
     - sparse-linear-algebra
     - stache
+    - stackage-curator
     - stateWriter
     - stm-containers
+    - store
     - streaming-commons
     - superbuffer
     - taggy