-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 code coverage in specific path mode #44625
Fix code coverage in specific path mode #44625
Conversation
base/compiler/utilities.jl
Outdated
m = moduleroot(m) | ||
mpath = pathof(m) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this how we define the path for coverage? I thought it was managed per-line in the table by the caller
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't think it was possible to be more specific in this function? Perhaps something other than this function is needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tried to make coverage info emission file-based but I'm hitting a BoundsError, so it appears the index handling needs more thought
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't figure out doing it on a line by line basis, so now it's enabled for all lines in a CodeInfo
if any of the lines fall in tracked files. Tests pass locally.
36bbb59
to
82a316e
Compare
82a316e
to
8b999b7
Compare
This fixes the codecov tests, and running the Octavian tests locally with CI enabled take the same time as master, so seems to not have a noticeable performance hit. |
@vtjnash I'm planning to merge this tomorrow, just in case you have any review/objection before then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm. Some small comments
Linux32 and win32 failures appear unrelated. The buildkite hang seems like a glitch? @DilumAluthge |
(cherry picked from commit feb7b77)
Fixes #44593