-
Notifications
You must be signed in to change notification settings - Fork 24
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
robust path management and package specification #31
Comments
Thanks for posting. Instead of
is it an option to use
In other words, require an actual |
I think it would be best to accept everything (including no argument), and just pass it on to We could then save the location (or maybe the whole coverage info) in |
Update: the above PR has been merged, so if that ends up in 1.9 then we can revisit this. |
Hey @tpapp, I'm currently doing some CI job using |
Can you describe the problem in detail? No, I do not recall seeing this. On a related note, I will revisit this issue soon but currently I have very little time. PRs welcome. |
I'll try to see if I can contribute. |
Unfortunately, that repo is somewhat outdated, I haven't used Gitlab for a while. |
@tpapp So I tested modifications of the path w.r.t the repo path and now coverage diff display works. I achieved this using a bit of |
Currently we map a package or a module to a path using undocumented internals (cf #30 which changes this).
I am not aware of a robust mechanism for doing this, other than calling internals. I wonder if we could just default to working on the current project.
It is still not clear how to query the path of the resulting cov files (again, other than hacks).
The text was updated successfully, but these errors were encountered: