Skip to content

doc: add an example of coverage paths normalization#593

Open
exoego wants to merge 1 commit into
k1LoW:mainfrom
exoego:normalization
Open

doc: add an example of coverage paths normalization#593
exoego wants to merge 1 commit into
k1LoW:mainfrom
exoego:normalization

Conversation

@exoego
Copy link
Copy Markdown
Contributor

@exoego exoego commented Dec 8, 2025

Because all of Ubuntu/Mac/Windows runners produce different coverage paths...
image

Normalization may be needed on other test matrix.

@k1LoW
Copy link
Copy Markdown
Owner

k1LoW commented Dec 8, 2025

Thank you!

However, your particular case seems rather unique for inclusion in the "Merging reports" section of the README.
Also, the example is specifically tailored to the lcov format.

@exoego
Copy link
Copy Markdown
Contributor Author

exoego commented Dec 8, 2025

The section already contains a matrix of different OSs.
So it makes sense to have this normalization.
Lcov is just an example and users should change (or remove) normalization logic.

@k1LoW
Copy link
Copy Markdown
Owner

k1LoW commented Dec 8, 2025

I see!
The Matrix example was bad, and the current example isn't working either.

Thank you!

@k1LoW
Copy link
Copy Markdown
Owner

k1LoW commented Dec 8, 2025

"The difference in path separators between operating systems" is unnecessary information for an example, so I'd like to modify the example.

k1LoW added a commit that referenced this pull request Feb 2, 2026
Change the example from OS-based matrix (macos/ubuntu/windows) to test
sharding to avoid confusion about cross-platform path separator handling, which is not relevant to the coverage merging feature itself.

Ref: #593
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.

2 participants