on master help sign in
put second-transfer test fail in right section (alcidesv/second-transfer#3)
09ef55fJens Petersen
build-constraints.yaml+3−3
@@ -1992,6 +1992,9 @@ expected-test-failures:
1992 # https://github.com/jgm/pandoc-citeproc/issues/172
1992 # https://github.com/jgm/pandoc-citeproc/issues/172
1993 - pandoc-citeproc
1993 - pandoc-citeproc
1994
1994
1995+ # https://github.com/alcidesv/second-transfer/issues/3
1996+ - second-transfer
1997+
1995# Haddocks which are expected to fail. Same concept as expected test failures.
1998# Haddocks which are expected to fail. Same concept as expected test failures.
1996expected-haddock-failures:
1999expected-haddock-failures:
1997 # https://github.com/acw/bytestring-progress/issues/4
2000 # https://github.com/acw/bytestring-progress/issues/4
@@ -2011,9 +2014,6 @@ expected-haddock-failures:
2011 # Not sure why, but it's a temporary package anyway
2014 # Not sure why, but it's a temporary package anyway
2012 - Cabal-ide-backend
2015 - Cabal-ide-backend
2013
2016
2014− # https://github.com/alcidesv/second-transfer/issues/3
2015− - second-transfer
2016−
2017# Benchmarks which should not be built. Note that Stackage does *not* generally
2017# Benchmarks which should not be built. Note that Stackage does *not* generally
2018# build benchmarks. The difference here will be whether dependencies for these
2018# build benchmarks. The difference here will be whether dependencies for these
2019# benchmarks are included or not.
2019# benchmarks are included or not.