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

Lcov file paths changed from absolute to relative #452

Closed
veke opened this issue Sep 16, 2021 · 3 comments
Closed

Lcov file paths changed from absolute to relative #452

veke opened this issue Sep 16, 2021 · 3 comments

Comments

@veke
Copy link

veke commented Sep 16, 2021 •
edited

Due to changed file paths in lcov file after v2.0.1 is breaking SonarQube integration for typescript coverage.

Change introduced in v2.0.2 and is now backwards incompatible.
@veke
Copy link
Author

veke commented Sep 16, 2021 •
edited

istanbuljs/istanbuljs#529 (comment)

Related comment

@veke veke changed the title Lcov file paths changed from relative to absolute Lcov file paths changed from absolute to relative Sep 16, 2021
@veke veke closed this as completed Sep 29, 2022
@veke
Copy link
Author

veke commented Sep 29, 2022

Updated Sonarqube version. Now understands relative paths.

@swendlandt
Copy link

Hello @veke, which SonarQube version did you need to update to to fix the issue?

We were running into the same issue when updating karma-coverage with SonarQube Version 9.9.2 (build 77730).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@veke @swendlandt