on master help sign in
drop bound for terminal-progress-bar (#1857)
commit909538ef4694ee8bd9be2bb7292f613bf3c8c43e authorJens Petersen <juhpetersen@gmail.com> dateMon 3 Oct 2016, 16:04 (10 years ago) parentec1ca34
1 file changed+1−4
build-constraints.yaml+1−4
build-constraints.yaml+1−4
@@ -2558,9 +2558,6 @@ packages:
25582558 # https://github.com/fpco/stackage/issues/1842
25592559 - dependent-sum < 0.4
25602560
2561− # https://github.com/fpco/stackage/issues/1857
2562− - terminal-progress-bar < 0.1.0 # Re-enable tests when lifting this
2563−
25642561 # https://github.com/fpco/stackage/issues/1863
25652562 - newtype-generics < 0.4 # May need to disable test suite when lifting this https://github.com/jcristovao/newtype-generics/issues/7
25662563 - MemoTrie < 0.6.5
@@ -2726,7 +2723,7 @@ skipped-tests:
27262723
27272724 # Blocked by stackage upper bounds. These can be re-enabled once
27282725 # the relevant stackage upper bound is lifted.
2729− - terminal-progress-bar # Fixed in 0.1.0 https://github.com/roelvandijk/terminal-progress-bar/issues/11
2726+
27302727
27312728 # Runtime issues
27322729 - blank-canvas # Never finishes https://github.com/ku-fpg/blank-canvas/issues/73