Repository navigation
Summarize test failures in the CI job summary and annotations - #2791
Merged
Benjamin Elder (BenTheElder) merged 6 commits intoOct 17, 2026
Merged
Benjamin Elder (BenTheElder) merged 6 commits into
Benjamin Elder (BenTheElder) merged 6 commits into
Conversation
drop -v from the gotestsum runs, with -json it replaces -test.v=test2json and go test stops marking t.Error output
otherwise verify only checks root.xml, and fails on a missing manifest when the unit tests fail
Collaborator
Author
|
Example, with temporary intentionally failing test commit: |
Benjamin Elder (BenTheElder)
force-pushed
the
ci-test-failure-summary
branch
from
October 17, 2026 02:13
be9e5a1 to
eb07a2d
Compare
Benjamin Elder (BenTheElder)
marked this pull request as ready for review
October 17, 2026 02:14
…t stacks, count package failures
Dmitry Berkovich (dberkov)
approved these changes
Oct 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Failures in the CI step logs have gotten hard to find, the unit test step alone is ~35k lines for a single failure.
junittool reportlists each failed test with just its t.Error / t.Fatal output in the job summary and as annotations.NOTE: There are some off the shelf tools, but we already had one, so tests aside this isn't much code and avoids taking another third party action dependency, while keeping our existing junit collection etc. It also folds a parent test into its failed subtests, names the tests that never finished on a timeout, and points panic annotations at the right line.
Tested locally with sample failures, against the artifacts from a failed main run, and on this PR with a since-dropped commit of failing unit tests.
AI-assisted.