on master help sign in
clarify description of expected-test-failures
6bfb1c7Jens Petersen
CURATORS.md+3−2
@@ -140,8 +140,9 @@ exist.
140### Expecting test/benchmark/haddock failures
140### Expecting test/benchmark/haddock failures
141
141
142The difference from the `skipped` sections is that items listed here
142The difference from the `skipped` sections is that items listed here
143−are compiled and their dependencies are taken into account. These
143+are compiled and their dependencies are taken into account
144+(but they are allowed to fail to build).
144−sections also have sub sections with groups and descriptions.
145+These sections also have subsections with groups and descriptions.
145
146
146One big category of test suites in this section are those requiring
147One big category of test suites in this section are those requiring
147running services. We don't want to run those, but we do want to check
148running services. We don't want to run those, but we do want to check
build-constraints.yaml+4−2
@@ -4350,8 +4350,10 @@ skipped-tests:
4350 - json-autotype # https://github.com/commercialhaskell/stackage/issues/4185
4350 - json-autotype # https://github.com/commercialhaskell/stackage/issues/4185
4351# end of skipped-tests
4351# end of skipped-tests
4352
4352
4353−# Tests which we should build and run, but which are expected to fail. We
4353+# Tests listed in expected-test-failures configure correctly but may fail to run
4354+# or even build correctly. A Stackage build should not fail based on a test build
4354−# should not fail a build based on a test failure for one of these packages.
4355+# or test run failure for these packages.
4356+# (Testsuites which can't configure should be placed under skipped-tests.)
4355expected-test-failures:
4357expected-test-failures:
4356
4358
4357 # GHC 8.4
4359 # GHC 8.4