on master help sign in
Add back stackage-curator (store-0.3.1 fixes memory issues)

Skips benchmark due to criterion, and adds store explicitly

commitae4c8919aecde1d3636d98ac02f28b6c3d8cd364 authorMichael Snoyman <michael@snoyman.com> dateThu 16 Feb 2017, 08:47 (10 years ago) parent5e83cd2
1 file changed+7−1
build-constraints.yaml+7−1
build-constraints.yaml+7−1
@@ -121,7 +121,8 @@ packages:
121121 - persistent-postgresql
122122 - persistent-sqlite
123123 - persistent-template
124− # - stackage-curator # via store https://github.com/fpco/stackage/issues/2283
124+ - stackage-curator
125+ - store
125126 - stm-conduit
126127 - wai-websockets
127128 - warp-tls
@@ -3046,6 +3047,9 @@ skipped-tests:
30463047 # via criterion: via cassava: bounds: vector
30473048 - sparse-linear-algebra
30483049
3050+ # criterion
3051+ - store
3052+
30493053# end of skipped-tests
30503054
30513055# Tests which we should build and run, but which are expected to fail. We
@@ -3462,8 +3466,10 @@ skipped-benchmarks:
34623466 - sourcemap
34633467 - sparse-linear-algebra
34643468 - stache
3469+ - stackage-curator
34653470 - stateWriter
34663471 - stm-containers
3472+ - store
34673473 - streaming-commons
34683474 - superbuffer
34693475 - taggy