Closed matt-graham closed 1 month ago
While it looks like the coverage reports aren't contributing to the runner disk space issues, given we don't use them and they mainly just add noise to the test logs (as does the captured log output) I still think this is a potentially useful quality of life improvement for when reading through the logs for failed tests, but happy to close if we think not worthwhile.
Removes step to generate HTML coverage report (and command line coverage report) in tests workflow as we don't use former at all as far as I'm aware, and the latter is not very helpful as it's generated per test file due to use of matrix job. Also prevents captured log /
stdout
output being shown on failing tests as this leads to very verbose logs and is rarely helpful in my opinion (tracebacks will still be shown). Aim with both these is to decrease size of artefacts being produced by test workflows to try to address issue of runners running out of disk space.