Skip to content

fix: distinguish suite results from test results#287

Merged
lidel merged 1 commit into
mainfrom
fix/250-suite-action
Apr 1, 2026
Merged

fix: distinguish suite results from test results#287
lidel merged 1 commit into
mainfrom
fix/250-suite-action

Conversation

@lidel

@lidel lidel commented Apr 1, 2026

Copy link
Copy Markdown
Member

JSON report now uses suite_pass/suite_fail actions for package-level events, so consumers no longer need to infer suite vs test by checking for the absence of a "Test" key.

@github-actions

github-actions Bot commented Apr 1, 2026

Copy link
Copy Markdown
Contributor

Results against Kubo master:

Summary

Tests Failures Errors Skipped
1263 0 0 0

@github-actions

github-actions Bot commented Apr 1, 2026

Copy link
Copy Markdown
Contributor

Results against Kubo latest:

Summary

Tests Failures Errors Skipped
1263 0 0 0

@lidel
lidel marked this pull request as ready for review April 1, 2026 00:58
Parse test2json NDJSON with encoding/json to reliably detect
package-level events and rename their pass/fail actions to
suite_pass/suite_fail.

- transformSuiteEvents uses json.Unmarshal to check for "Test" key
- bytes.SplitSeq/bytes.Replace avoid string conversions
- add TestTransformSuiteEvents
@lidel
lidel force-pushed the fix/250-suite-action branch from 58ad5d8 to 449b384 Compare April 1, 2026 01:11
@lidel
lidel merged commit 73d5fde into main Apr 1, 2026
10 checks passed
@lidel
lidel deleted the fix/250-suite-action branch April 1, 2026 01:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Test suite failure hard to distinguish from test failure

1 participant