REF-17: Publish CI test report and fix Node 20 action deprecation - #91
Merged
Conversation
The Build workflow ran `mvn clean install` but never surfaced the Surefire results, so no test report was visible on the run or PR. Add two first-party, always-run steps: - Publish test summary: a stdlib-only Python script parses every target/surefire-reports/TEST-*.xml and writes an aggregated pass/fail table (plus any failing tests) to the GitHub run summary. - Upload Surefire reports as a build artifact for offline inspection. Both use `if: always()` so the report is produced even when the Maven step fails on a test failure. Also bump the actions off the deprecated Node 20 runtime: checkout v4 -> v5, setup-java v4 -> v5, and the new upload-artifact pinned to v6 (all Node 24). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The Build workflow ran
mvn clean installbut never surfaced the Surefire results, so no test report was visible on the run or PR. It also emitted a Node 20 deprecation warning for the pinned actions.Changes
.github/scripts/test-summary.pyparses everytarget/surefire-reports/TEST-*.xml, aggregates across modules, and writes a pass/fail table plus any failing tests to the GitHub run Summary page.actions/upload-artifact@v6) for offline inspection of failure detail.if: always(), so the report is produced even when the Maven step fails on a test failure (otherwise the report would be skipped exactly when it's most useful).actions/checkout@v4 → v5,actions/setup-java@v4 → v5, and the newupload-artifactpinned tov6. Verified each action'sruns.using:checkout@v5/setup-java@v5are Node 24, butupload-artifact@v5is still Node 20, so v6 (the first Node-24 major) is used.No third-party actions are introduced (first-party only).
Verification
🤖 Generated with Claude Code