[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4188: Test results are harder to read on GitHub Actions

[Tahoe-LAFS]

#4188: Test results are harder to read on GitHub Actions
---------------------+---------------------------
 Reporter:  sajith   |          Owner:
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:  undecided
Component:  unknown  |        Version:  n/a
 Keywords:           |  Launchpad Bug:
---------------------+---------------------------
 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:

 https://app.circleci.com/pipelines/github/tahoe-lafs/tahoe-
 lafs/5362/workflows/d9bcd1bc-a039-425e-aed9-f0697961532b/jobs/91649/tests

 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 [https://circleci.com/docs/guides/test/collect-
 test-data/ store_test_results] step.  I suppose we could follow similar
 steps with GHA.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4188>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage