-
-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Running tests with buildRustCrate #59177
Comments
I'm indeed interested in this topic, but I'm afraid I don't have much time to work on it right now. If you want to implement it, I'd be happy to review. The way to go is to look at what Then doc tests can be built and run using I don't think any change needs to be done to Carnix, but don't hesitate to tell me if you need something done in Carnix. |
On thing that is important to me and I would like advice on is having separate derivations for
That way, we only do the necessary rustc invocations if something changes during development. It would still be nice if the derivations could still be created with one function call similarly to A) Create a new function that returns a attribute set with a bunch of derivations, keyed by e.g. B) Make C) Make I prefer A but I'd like to hear the opinions of more experienced "nixers". |
@andir This is basically done, isn't it? |
@kolloch yes it kind of is done. Is there a need to have proper execution in nixpkgs? I think it would be a honorable long-term goal. |
Oh, I just found out about crate2nix. What was wrong with carnix? How does crate2nix fix it? Are you interested in merging the projects? |
While we probably shouldn't have the conversation here but on either of the issue trackers. I'll try to summarize the benefits from my personal perspective (not offensive towards carnix):
|
@P-E-Meunier : I'd love to chat but I have trouble contacting you. I send you a message on lobste.rs and tried to do the same on IRC. Email would be terribly convenient for me. |
Issue description
buildRustCrate
can be used to build binary, library and procmacro crates but I think tests are not yet supported. (I'd be happy if I am wrong!)I think having separate build tooling for running tests is not optimal:
I'd be interested in the full range of
It is probably good to separate building tests from running tests.
Pinging some potentially interested users (sorry if you are not interested in this topic): @P-E-Meunier @vitiral @Mic92
I gladly take a full solution but I'd also be interested in pointers in how other languages solve this with nix or and outline on what would be a idiomatic way to achieve this.
The text was updated successfully, but these errors were encountered: