git.iko.soy/stackage
on master help sign in
clarify description of expected-test-failures
commit6bfb1c74079e349db9e0e653f3e199109630259e authorJens Petersen <juhpetersen@gmail.com> dateWed 9 Jan 2019, 11:46 (8 years ago) parent9bf99b5
2 files changed+7−4
compare with master
unifiedsplit
CURATORS.md+3−2 build-constraints.yaml+4−2
CURATORS.md+3−2
@@ -140,8 +140,9 @@ exist.
140140### Expecting test/benchmark/haddock failures
141141
142142The difference from the `skipped` sections is that items listed here
143−are compiled and their dependencies are taken into account. These
144−sections also have sub sections with groups and descriptions.
143+are compiled and their dependencies are taken into account
144+(but they are allowed to fail to build).
145+These sections also have subsections with groups and descriptions.
145146
146147One big category of test suites in this section are those requiring
147148running 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:
43504350 - json-autotype # https://github.com/commercialhaskell/stackage/issues/4185
43514351# end of skipped-tests
43524352
4353−# Tests which we should build and run, but which are expected to fail. We
4354−# should not fail a build based on a test failure for one of these packages.
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
4355+# or test run failure for these packages.
4356+# (Testsuites which can't configure should be placed under skipped-tests.)
43554357expected-test-failures:
43564358
43574359 # GHC 8.4