-
Notifications
You must be signed in to change notification settings - Fork 96
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
Expose whether bin/lib target has tests enabled #114
Comments
The information isn't exposed from Cargo. The additional fields need to be added to |
Oh I see... Btw, the comment "Serialized as a list of strings for historical reasons" for the |
No. The documentation that explains the fields is here. I'm only guessing, but I think it would have been preferred for libraries to have a value of |
Oh wow, I think Miri is getting that wrong then... we just check for "lib". The "etc" doesn't exactly help when one wants to be sure to cover all lib crates.^^ |
Uh... so is there any action that I can do about this in |
It's not resolved but blocked on cargo exposing |
Emit the `test` field in cargo metadata This is needed so `cargo-metadata` can expose it: oli-obk/cargo_metadata#114
The cargo PR has been merged |
Awesome. :D |
no, we need to wait for this information to make it to a release and then add the appropriate field |
There currently seems to be no way to figure out if a bin/lib target has tests enabled. Would be great if that information was made available -- I think that is required to solve rust-lang/miri#700.
The text was updated successfully, but these errors were encountered: