From: "Daniel Schäfer" <git@danielschaefer.me>
Cc: guix-devel@gnu.org
Subject: Re: Fwd: Running individual system tests
Date: Wed, 23 Oct 2019 14:03:20 +0200 [thread overview]
Message-ID: <20cc7df7-89bd-120b-d18d-c4a5b3bbbda3@danielschaefer.me> (raw)
In-Reply-To: <d7e48011-cc78-2b9e-d956-ae8cc3f72150@danielschaefer.me>
So you're saying, I have to run
```
./bootstrap
./configure
make
./pre-inst-env guix build my-new-package
```
which builds the daemon, and compiles all Guile modules?
And I have to do it, whenever I want to run any system test, or build an
in-tree package (which I'm going to submit for inclusion)?
Or more precisely: It has to be run, once, before I do those things.
Question: Doesn't it ever have to be rerun? How are new modules compiled?
It takes 33 minutes on my laptop and is only going to take longer, when
Guix gets bigger.
Is there maybe an interpreted mode? Or could this be better with Guile
3.0 JIT?
- Daniel
On 10/21/19 8:43 AM, Daniel Schäfer wrote:
> Hi Ricardo,
>
> For a test of an external system, like something I develop at work, I
> don't want/need to have Guix with all modules compiled present.
> I don't want unnecessary steps if they are not necessary.
>
> Please refer to my first mail with an example of running a test
> standalone.
> I'd like some assistance to make my snippet nicer and not return an
> error after successfully running the test.
>
> Thanks,
> Daniel
>
> On 10/19/19 7:35 PM, Ricardo Wurmus wrote:
>> Hi Daniel,
>>
>> I don’t understand why you would want to run a system test without
>> building Guix first.
>>
>> Could you elaborate?
>>
next prev parent reply other threads:[~2019-10-23 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e9c67f90-8c08-7019-1dbc-a4cd09704728@danielschaefer.me>
2019-10-19 10:06 ` Fwd: Running individual system tests Daniel Schäfer
2019-10-19 11:27 ` Marius Bakke
2019-10-19 17:35 ` Ricardo Wurmus
2019-10-21 6:43 ` Daniel Schäfer
2019-10-23 12:03 ` Daniel Schäfer [this message]
2019-10-23 13:04 ` Danny Milosavljevic
2019-10-23 16:02 ` Fwd: " Ricardo Wurmus
2019-10-25 20:28 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20cc7df7-89bd-120b-d18d-c4a5b3bbbda3@danielschaefer.me \
--to=git@danielschaefer.me \
--cc=guix-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).