From 09ef55f19a681f0e7ad964bd49884aed7e05e9b5 Mon Sep 17 00:00:00 2001 From: Jens Petersen Date: Tue, 6 Oct 2015 20:07:19 +0900 Subject: [PATCH] put second-transfer test fail in right section (alcidesv/second-transfer#3) --- build-constraints.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/build-constraints.yaml b/build-constraints.yaml index a85f1a48..676a0509 100644 --- a/build-constraints.yaml +++ b/build-constraints.yaml @@ -1992,6 +1992,9 @@ expected-test-failures: # https://github.com/jgm/pandoc-citeproc/issues/172 - pandoc-citeproc + # https://github.com/alcidesv/second-transfer/issues/3 + - second-transfer + # Haddocks which are expected to fail. Same concept as expected test failures. expected-haddock-failures: # https://github.com/acw/bytestring-progress/issues/4 @@ -2011,9 +2014,6 @@ expected-haddock-failures: # Not sure why, but it's a temporary package anyway - Cabal-ide-backend - # https://github.com/alcidesv/second-transfer/issues/3 - - second-transfer - # Benchmarks which should not be built. Note that Stackage does *not* generally # build benchmarks. The difference here will be whether dependencies for these # benchmarks are included or not.