Opened at 2025-12-09T16:31:25Z
Last modified at 2025-12-09T16:31:42Z
#4188 new defect
Test results are harder to read on GitHub Actions
| Reported by: | sajith | Owned by: | sajith |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | unknown | Version: | n/a |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
When some tests fail on GitHub Actions CI, it is tedious to figure out exactly which tests failed and why. This is is somewhat easier on CircleCI, because there is a tab that shows which tests failed, with some details. For example, see the tests tab on:
Now compare that with: https://github.com/tahoe-lafs/tahoe-lafs/actions/runs/19959845121/job/57237405534.
With GitHub Actions, our options are to manually grep through the raw log, or run gh run view --log-failed --job=57237405534. (Note that gh is GitHub CLI.)
It looks like there is a third option: it should be possible to achieve a similar thing as CircleCI on GitHub Actions using https://github.com/dorny/test-reporter.
On CircleCI we use SUBUNITREPORTER_OUTPUT_PATH: "test-results.subunit2" twisted.trial --reporter=subunitv2-file ..., and then subunit2junitxml.exe --output-to=test-results.xml test-results.subunit2, which gets stored in a store_test_results step. I suppose we could follow similar steps with GHA.
