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.

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

fix(coverage): Account for SHA in lcov DA parsing #6463

Merged

Conversation

blorente
Copy link
Collaborator

@blorente blorente commented Jun 4, 2024

Checklist

  • I have filed an issue about this change and discussed potential changes with the maintainers.
  • I have received the approval from the maintainers to make this change.
  • This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.

Discussion thread for this change

N/A

Description of this change

Some coverage formats include a SHA in their report. In those cases, the parser failed and no coverage was reported. This PR fixes that.

@github-actions github-actions bot added product: IntelliJ IntelliJ plugin awaiting-review Awaiting review from Bazel team on PRs labels Jun 4, 2024
@agluszak
Copy link
Collaborator

agluszak commented Jun 4, 2024

Ideally there should be a test for that

@blorente blorente force-pushed the blorente/account-for-sha-in-lcov branch from a2d698a to a2b065b Compare June 6, 2024 08:35
@blorente
Copy link
Collaborator Author

blorente commented Jun 6, 2024

@agluszak Good point! Added a unit test based on real data.

@blorente blorente merged commit ff5d037 into bazelbuild:master Jun 6, 2024
6 checks passed
@github-actions github-actions bot removed the awaiting-review Awaiting review from Bazel team on PRs label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product: IntelliJ IntelliJ plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants