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

Recorder returns code coverage for scoped trace points as 0. #130

Open
gauravAshok opened this issue May 8, 2017 · 1 comment
Open

Recorder returns code coverage for scoped trace points as 0. #130

gauravAshok opened this issue May 8, 2017 · 1 comment
Assignees
@janmejay

Comments

@gauravAshok
Copy link

For trace points A and B where B is "PARENT_SCOPED" under A and marked with x% & y% code coverage respectively, the /profile indices contain a trace name "B > A" with code_coverage 0.
This may also happen with other mergeSematics where a new trace point name is created.
@janmejay janmejay mentioned this issue May 9, 2017
Merged
@janmejay
Copy link

@gauravAshok we need to verify and close this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@janmejay janmejay

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@janmejay @gauravAshok