-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
cli: add show-env subcommand #115
Conversation
Thanks!
We are going to remove this environment variable in #112. Perhaps that will fix this problem?
Hmm... I'll take a look later. |
Yep, rebasing has fixed that, nice 👍
Added. Note you can use this one-liner even:
|
Pushed some tidy and test fixes, and added a short note to the README based on the comment in #93. |
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
bors r+ |
Build succeeded! And happy new year! 🎉 |
Thanks, sorry for the slow review turnaround, have been busy over the festive season! |
Published in 0.1.14.
No problem. (The only reason I applied the changes myself was to avoid conflicts with a subsequent huge patch.) |
IIUC, the problem is that cargo-llvm-cov and cargo refer to different build artists, so I guess it will work if passing |
Turns out it was partly this and also that for various reasons some of the build output was going into the Thanks again! |
Implements the
show-env
suggestion from #93 (comment)An example output:
After exporting these vars, I had a go at building pyo3's
cdylib
examples and then running them withpytest
.Pleased to see that I do get profile output in the expected location:
There's still some pain points:
CARGO_TARGET_DIR
before attempting to runcargo llvm-cov
command, or I get crashes because it tries to appendllvm-cov-target
for a second time:CARGO_TARGET_DIR
, I still get a failure to generate the report. I suspect this is becausecargo-llvm-cov
is not finding and passing thecdylib
outputs tollvm-cov report
?If you're interested, you can see the companion PyO3 at PyO3/pyo3#2067