clarify description of expected-test-failures

This commit is contained in:
Jens Petersen 2019-01-09 11:46:46 +09:00
parent 9bf99b5d5c
commit 6bfb1c7407
2 changed files with 7 additions and 4 deletions

View File

@ -140,8 +140,9 @@ exist.
### Expecting test/benchmark/haddock failures ### Expecting test/benchmark/haddock failures
The difference from the `skipped` sections is that items listed here The difference from the `skipped` sections is that items listed here
are compiled and their dependencies are taken into account. These are compiled and their dependencies are taken into account
sections also have sub sections with groups and descriptions. (but they are allowed to fail to build).
These sections also have subsections with groups and descriptions.
One big category of test suites in this section are those requiring One big category of test suites in this section are those requiring
running services. We don't want to run those, but we do want to check running services. We don't want to run those, but we do want to check

View File

@ -4350,8 +4350,10 @@ skipped-tests:
- json-autotype # https://github.com/commercialhaskell/stackage/issues/4185 - json-autotype # https://github.com/commercialhaskell/stackage/issues/4185
# end of skipped-tests # end of skipped-tests
# Tests which we should build and run, but which are expected to fail. We # Tests listed in expected-test-failures configure correctly but may fail to run
# should not fail a build based on a test failure for one of these packages. # or even build correctly. A Stackage build should not fail based on a test build
# or test run failure for these packages.
# (Testsuites which can't configure should be placed under skipped-tests.)
expected-test-failures: expected-test-failures:
# GHC 8.4 # GHC 8.4