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

File paths in coverage information are just the package name #67

Closed
siddharthab opened this issue Apr 2, 2021 · 0 comments · Fixed by #70
Closed

File paths in coverage information are just the package name #67

siddharthab opened this issue Apr 2, 2021 · 0 comments · Fixed by #70

Comments

@siddharthab
Copy link
Collaborator

We stopped using the full path to the package in the staging area in b43af01, because of which coverage collector no longer knew the full path to the original source files, and so the coverage xml only has the package name instead of the path.

siddharthab pushed a commit that referenced this issue Apr 2, 2021
This helps us test whether we make the right distinction between package
paths and package names in various places.

As part of this, some fixes to path handling have been made throughout.

Fixes #67.
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 a pull request may close this issue.

1 participant