From: John Soo <jsoo1@asu.edu>
To: Andreas Rottmann <mail@r0tty.org>
Cc: guix-devel@gnu.org
Subject: Re: (not) testing Rust packages?!
Date: Fri, 31 Jan 2020 10:50:38 -0800 [thread overview]
Message-ID: <6DE68DE8-AA88-4E77-A51D-85D9CC55153A@asu.edu> (raw)
In-Reply-To: <87eevixf20.fsf@londo.h.r0tty.org>
Hi Andreas,
> On Jan 29, 2020, at 11:01 AM, Andreas Rottmann <mail@r0tty.org> 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.
> Having tests run would be great: it's a service to the Rust ecosystem,
> and can also help catch issues in packaging, as was already pointed
> out. How likely catching issues is depends on the testsuite quality of
> the crate in question, but that's not at all an argument against running
> tests, of course!
Agreed.
> This may have come across wrong: I just wanted to point out that it may
> mean more packaging effort, but it seems Guix is in a good position here
> already.
Ah yeah I probably came across wrong, too. You are definitely right that there will be more packaging effort. I think at some point it should get easier once the popular test dependencies get in.
What do you think?
John
next prev parent reply other threads:[~2020-01-31 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 13:38 (not) testing Rust packages?! Hartmut Goebel
2020-01-25 14:31 ` Martin Becze
2020-01-25 16:46 ` John Soo
2020-01-25 17:45 ` Martin Becze
2020-01-25 22:56 ` Andreas Rottmann
2020-01-27 14:49 ` John Soo
2020-01-29 19:01 ` Andreas Rottmann
2020-01-31 18:50 ` John Soo [this message]
2020-02-03 12:22 ` Hartmut Goebel
2020-01-25 18:55 ` Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6DE68DE8-AA88-4E77-A51D-85D9CC55153A@asu.edu \
--to=jsoo1@asu.edu \
--cc=guix-devel@gnu.org \
--cc=mail@r0tty.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.