all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 49981@debbugs.gnu.org
Subject: [bug#49981] wip: Introduce unit-tests.
Date: Thu, 12 Aug 2021 16:50:56 +0200	[thread overview]
Message-ID: <87a6lm3een.fsf@gnu.org> (raw)
In-Reply-To: <87im0di2t1.fsf@cbaines.net> (Christopher Baines's message of "Tue, 10 Aug 2021 19:15:38 +0100")


Hello Chris,

> Converting the tests themselves in to things that have to be put in the
> store to be run could make local development harder, and is a step
> towards making guix harder to package and distribute. As an example, it
> would probably be possible for the Debian package to continue running
> the tests, but I'd expect that having to run a guix-daemon just to be
> able to setup for the tests will make running them more difficult.

That's a valid objection. Regarding the "current-guix" package, it
builds the unit tests as a whole and it would be hard to extract
precisely the result of each individual test.

As almost everything else in Guix is somehow a derivation, it would be
easier for Cuirass to deal with the unit tests under that format. Maybe
we would need to find a way to be able to run them under the actual
form, as well as under a derivation format. This needs more thoughts
though, so I'll put that on hold.

Thanks for the feedback,

Mathieu




  reply	other threads:[~2021-08-12 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 15:04 [bug#49981] wip: Introduce unit-tests Mathieu Othacehe
2021-08-10 18:15 ` Christopher Baines
2021-08-12 14:50   ` Mathieu Othacehe [this message]
2021-08-10 18:23 ` Maxime Devos
2021-08-30 20:14 ` Maxim Cournoyer
2021-08-31  6:27   ` zimoun
2021-08-31  6:36 ` zimoun

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=87a6lm3een.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=49981@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /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.