From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?Daniel_Sch=c3=a4fer?= <git@danielschaefer.me>
Subject: Fwd: Running individual system tests
Date: Sat, 19 Oct 2019 12:06:25 +0200
Message-ID: <7a1ea893-6ec0-5312-a013-cdc246a1e1e5@danielschaefer.me>
References: <e9c67f90-8c08-7019-1dbc-a4cd09704728@danielschaefer.me>
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------4F4BB7D907A75490861B1851"
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:49812)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <git@danielschaefer.me>) id 1iLld6-0005k3-Vq
 for guix-devel@gnu.org; Sat, 19 Oct 2019 06:06:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <git@danielschaefer.me>) id 1iLld5-0001xq-48
 for guix-devel@gnu.org; Sat, 19 Oct 2019 06:06:36 -0400
Received: from ciffreo.uberspace.de ([185.26.156.173]:55806)
 by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <git@danielschaefer.me>)
 id 1iLld4-0001sT-Pc
 for guix-devel@gnu.org; Sat, 19 Oct 2019 06:06:35 -0400
In-Reply-To: <e9c67f90-8c08-7019-1dbc-a4cd09704728@danielschaefer.me>
Content-Language: en-US
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: guix-devel@gnu.org

This is a multi-part message in MIME format.
--------------4F4BB7D907A75490861B1851
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Guix developers,

I'm still trying to figure out, how to run a single Guix system test 
without building the entirety of Guix.
Does anybody do this? Has anybody written a Guix system test for 
something not in Guix? Maybe a personal or work-related project.

CC'ing some people who've added guix system tests.

Thanks,
Daniel

-------- Forwarded Message --------
Subject: 	Running individual system tests
Date: 	Tue, 15 Oct 2019 13:21:45 +0200
From: 	Daniel Schäfer <daniel@danielschaefer.me>
To: 	help-guix@gnu.org



Hi Guix,

Guix System has nice system tests, as described in [1] but they don't 
easily allow to run a single test.

The manual says to run `make check-system TESTS="basic mcron"` in the 
guix source tree.
That, however, (apparently) requires to be bootstrapped, configured and 
all Scheme files to be fully built.

Is there something as simple as:

$ guix build -f gnu/tests/rsync.scm
guix build: error: #<unspecified>: not something we can build

---

I hacked together a solution that works but is far from nice.
It is based off of build-aux/run-system-tests.scm and I tried to strip 
it down to the core.

$ cat run-test.scm
(use-modules (gnu tests rsync)
              (gnu tests)
              (guix store)
              (guix status)
              (guix monads)
              (guix derivations)
              (guix ui)
              (srfi srfi-1)
              (srfi srfi-34))

(define (built-derivations* drv)
   (lambda (store)
     (guard (c ((store-protocol-error? c)
                (values #f store)))
       (values (build-derivations store drv) store))))

(system-test-value %test-rsync)
   (with-store store
     (with-status-verbosity 2
       (run-with-store store
         (mlet* %store-monad ((drv (mapm %store-monad system-test-value 
(list %test-rsync)))
                              (out -> (map derivation->output-path drv)))
           (mbegin %store-monad
             (show-what-to-build* drv)
             (set-build-options* #:keep-going? #t #:keep-failed? #t
                                 #:print-build-trace #t
                                 #:print-extended-build-trace? #t
                                 #:fallback? #t)
             (built-derivations* drv)
             (display out))))))

$ guile -s run-test.scm
(/gnu/store/scifaigbvcj20lplj3mvqj3ndr9w0nlv-rsync-test)Backtrace:
            8 (apply-smob/1 #<catch-closure 7353e0>)
In ice-9/boot-9.scm:
     705:2  7 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
In ice-9/eval.scm:
     619:8  6 (_ #(#(#<directory (guile-user) 7cd140>)))
In ice-9/boot-9.scm:
    2312:4  5 (save-module-excursion _)
   3831:12  4 (_)
In /home/zoid/guix/gnu/tests/run-test.scm:
      19:4  3 (_)
In guix/status.scm:
     810:4  2 (call-with-status-report _ _)
In guix/store.scm:
   1737:24  1 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
In unknown file:
            0 (_ #<store-connection 256.99 3b8dd20>)

ERROR: Wrong type to apply: #<unspecified>


It shows the derivation output path before the backtrace and thus I can 
inspect the log.
Can I do this in a nicer way?
It would be very helpful for out-of-tree system tests.

Thanks

- Daniel

[1] https://guix.gnu.org/blog/2016/guixsd-system-tests/



--------------4F4BB7D907A75490861B1851
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><tt>Hi Guix developers,</tt></p>
    <p><tt>I'm still trying to figure out, how to run a single Guix
        system test without building the entirety of Guix.<br>
        Does anybody do this? Has anybody written a Guix system test for
        something not in Guix? Maybe a personal or work-related project.<br>
      </tt></p>
    <p><tt>CC'ing some people who've added guix system tests.<br>
      </tt></p>
    <p><tt>Thanks,<br>
        Daniel</tt><br>
    </p>
    <div class="moz-forward-container">-------- Forwarded Message
      --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>Running individual system tests</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Tue, 15 Oct 2019 13:21:45 +0200</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td>Daniel Schäfer <a class="moz-txt-link-rfc2396E" href="mailto:daniel@danielschaefer.me">&lt;daniel@danielschaefer.me&gt;</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:help-guix@gnu.org">help-guix@gnu.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      Hi Guix,<br>
      <br>
      Guix System has nice system tests, as described in [1] but they
      don't easily allow to run a single test.<br>
      <br>
      The manual says to run `make check-system TESTS="basic mcron"` in
      the guix source tree.<br>
      That, however, (apparently) requires to be bootstrapped,
      configured and all Scheme files to be fully built.<br>
      <br>
      Is there something as simple as:<br>
      <br>
      $ guix build -f gnu/tests/rsync.scm<br>
      guix build: error: #&lt;unspecified&gt;: not something we can
      build<br>
      <br>
      ---<br>
      <br>
      I hacked together a solution that works but is far from nice.<br>
      It is based off of build-aux/run-system-tests.scm and I tried to
      strip it down to the core.<br>
      <br>
      $ cat run-test.scm<br>
      (use-modules (gnu tests rsync)<br>
                   (gnu tests)<br>
                   (guix store)<br>
                   (guix status)<br>
                   (guix monads)<br>
                   (guix derivations)<br>
                   (guix ui)<br>
                   (srfi srfi-1)<br>
                   (srfi srfi-34))<br>
      <br>
      (define (built-derivations* drv)<br>
        (lambda (store)<br>
          (guard (c ((store-protocol-error? c)<br>
                     (values #f store)))<br>
            (values (build-derivations store drv) store))))<br>
      <br>
      (system-test-value %test-rsync)<br>
        (with-store store<br>
          (with-status-verbosity 2<br>
            (run-with-store store<br>
              (mlet* %store-monad ((drv (mapm %store-monad
      system-test-value (list %test-rsync)))<br>
                                   (out -&gt; (map
      derivation-&gt;output-path drv)))<br>
                (mbegin %store-monad<br>
                  (show-what-to-build* drv)<br>
                  (set-build-options* #:keep-going? #t #:keep-failed? #t<br>
                                      #:print-build-trace #t<br>
                                      #:print-extended-build-trace? #t<br>
                                      #:fallback? #t)<br>
                  (built-derivations* drv)<br>
                  (display out))))))<br>
      <br>
      $ guile -s run-test.scm<br>
      (/gnu/store/scifaigbvcj20lplj3mvqj3ndr9w0nlv-rsync-test)Backtrace:<br>
                 8 (apply-smob/1 #&lt;catch-closure 7353e0&gt;)<br>
      In ice-9/boot-9.scm:<br>
          705:2  7 (call-with-prompt _ _ #&lt;procedure
      default-prompt-handle…&gt;)<br>
      In ice-9/eval.scm:<br>
          619:8  6 (_ #(#(#&lt;directory (guile-user) 7cd140&gt;)))<br>
      In ice-9/boot-9.scm:<br>
         2312:4  5 (save-module-excursion _)<br>
        3831:12  4 (_)<br>
      In /home/zoid/guix/gnu/tests/run-test.scm:<br>
           19:4  3 (_)<br>
      In guix/status.scm:<br>
          810:4  2 (call-with-status-report _ _)<br>
      In guix/store.scm:<br>
        1737:24  1 (run-with-store _ _ #:guile-for-build _ #:system _ #
      _)<br>
      In unknown file:<br>
                 0 (_ #&lt;store-connection 256.99 3b8dd20&gt;)<br>
      <br>
      ERROR: Wrong type to apply: #&lt;unspecified&gt;<br>
      <br>
      <br>
      It shows the derivation output path before the backtrace and thus
      I can inspect the log.<br>
      Can I do this in a nicer way?<br>
      It would be very helpful for out-of-tree system tests.<br>
      <br>
      Thanks<br>
      <br>
      - Daniel<br>
      <br>
      [1] <a class="moz-txt-link-freetext" href="https://guix.gnu.org/blog/2016/guixsd-system-tests/">https://guix.gnu.org/blog/2016/guixsd-system-tests/</a><br>
      <br>
      <br>
    </div>
  </body>
</html>

--------------4F4BB7D907A75490861B1851--