|
From: | Daniel Schäfer |
Subject: | Re: Fwd: Running individual system tests |
Date: | Wed, 23 Oct 2019 14:03:20 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 |
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?
[Prev in Thread] | Current Thread | [Next in Thread] |