Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

dotnet-coverage merge marks cobertura files as invalid when different keyboard/OS language is being used #130

Closed
CssaBee opened this issue Aug 27, 2024 · 1 comment
Closed

dotnet-coverage merge marks cobertura files as invalid when different keyboard/OS language is being used #130

CssaBee opened this issue Aug 27, 2024 · 1 comment
Assignees
@fhnaseer
Labels
bug Something isn't working sprint

Comments

@CssaBee
Copy link

CssaBee commented Aug 27, 2024 •
edited by pavelhorak
Loading

Using even the sample from https://gcovr.com/en/stable/output/cobertura.html, 'dotnet-coverage merge' marks it as an invalid file.
Changing all the dots to commas (representing numbers, e.g. 5.0 vs 5,0) suddenly everything starts to work again.

Using the tool should be language independent and parse cobertura files using dots only for number representation.

AB#2242145
@fhnaseer fhnaseer added the bug Something isn't working label Aug 27, 2024
@fhnaseer fhnaseer self-assigned this Sep 6, 2024
@fhnaseer fhnaseer added the sprint label Sep 6, 2024
@fhnaseer
Copy link
Member

fhnaseer commented Sep 9, 2024 •
edited
Loading

This has been fixed and will be available in the next release (17.12.4).

@fhnaseer fhnaseer closed this as completed Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fhnaseer fhnaseer

Labels
bug Something isn't working sprint
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fhnaseer @CssaBee