-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Combining nextest, llvm-cov and delayed execution #1036
Comments
Don't get confused by the example, I named the target |
IIRC, this |
You're correct, I tried the second one and it suffers from the same issue |
envvars.sh internally call |
|
Export works, no profraws though :/ |
|
Oh, that's about the builtin nextest subcommand, so that may not work for show-env as-is. (That said, the underlying problem should probably be the same.) |
I'm not sure I understand the issue, profraws should be generated during compilation and they don't get packaged with
Added it, but I checked and there are just no .profraw's after the test run |
|
No, binary (or cdylib) will generate *.profraw file on exit. See also taiki-e/cargo-llvm-cov#320 (comment).
Does this mean it cannot be found using In the latter case, I guess the problem is that the target directory used by --archive-file is different from cargo's default, just like the problem that occurred in the linked PR, so I think it can be avoided by adjusting |
Here, I made a repro repository, the problem is in the issue |
Solved thanks to a friend, repro contains the solution |
Hello, I'm investing how I can create an optimal integration test environment and that includes code coverage and junit compatible test logs, while efficiently using build cache.
I believe cargo-llvm-cov combined with nextest it possible, but I'm having some trouble executing it and I was hoping someone could help me out here.
The
run-report.sh
The issue I'm running into is that the profraws aren't being generated and I believe this has to do with the nextest building process.
Any ideas?
The text was updated successfully, but these errors were encountered: