[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (not) testing Rust packages?!

From: Hartmut Goebel
Subject: Re: (not) testing Rust packages?!
Date: Mon, 3 Feb 2020 13:22:57 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2

Am 31.01.20 um 19:50 schrieb John Soo:
>> On Jan 29, 2020, at 11:01 AM, Andreas Rottmann <address@hidden> wrote:
>> I'm a new to Guix, and am not sure what you mean by "safely" and
>> "unwanted store outputs". Running `cargo test` takes the crate source,
>> and the closure of any `dependencies` and `dev-dependencies`, and
>> produces no real artifacts that make sense to put in the store, as far
>> as I can see. The only noteworthy artifact is the stdout/stderr ouput
>> produced, as well as the exit status, but I guess that's not relevant to
>> the store.
> Oh I could see how “safely” would be confusing. I meant that we would not 
> populate anything in the store as you suggest.

If `cargo test` does not "install" any file - and this is what I would
expect it to do, since this is what `cargo install` - running `cargo
test` is save.

Neither the exit status nor the stderr/stdout output are effecting the

> What do you think? 

Go ahead! :-)

Hartmut Goebel

| Hartmut Goebel          | address@hidden               |
| | compilers which you thought are impossible |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]