From: "Clément Lassieur" <clement@lassieur.org>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: help-guix@gnu.org
Subject: Re: Cuirass fibers crash // using with GUIX_PACKAGE_PATH
Date: Thu, 09 Aug 2018 19:33:33 +0200 [thread overview]
Message-ID: <87h8k3phqq.fsf@lassieur.org> (raw)
In-Reply-To: <idjwosz7erh.fsf@bimsb-sys02.mdc-berlin.net>
Hi Ricardo,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> Hi Guix,
>
> I have a server running GuixSD with Cuirass and it’s supposed to build a
> bunch of user-provided manifests continuously. These manifests refer to
> packages that are defined in a separate repository that is on
> GUIX_PACKAGE_PATH, so really the Cuirass specification for them depends
> on two repositories. Can we express this with specifications?
Yes, the Cuirass manual shows an example that does exactly what you
want:
'((#:name . "foo-master")
(#:load-path-inputs . ("guix"))
(#:package-path-inputs . ("packages"))
(#:proc-input . "conf")
(#:proc-file . "drv-list.scm")
(#:proc . cuirass-jobs)
(#:proc-args (subset . "foo"))
(#:inputs . (((#:name . "guix")
(#:url . "git://git.savannah.gnu.org/guix.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t))
((#:name . "conf")
(#:url . "git://my-personal-conf.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t))
((#:name . "packages")
(#:url . "git://my-custom-packages.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t)))))
> Previously I set up a cron job to update the second repository and
> added it on the load-path through the Cuirass service configuration.
That cron job is not needed anymore. Also, that load-path isn't global
any longer: it's per specification (see #:package-path-inputs).
> Since a recent update to Cuirass and the service “load-path” is no
> longer a valid field, so it seems I can no longer do this. Do you have
> any recommendations on how to accomplish my goal?
Indeed, that recent update you are talking about adds multiple inputs to
a Cuirass specification. Its goal is to handle your use case in a
better way: the GUIX_PACKAGE_PATH (named "packages" in the above
example) is a new input, and a new evaluation will be triggered when a
new commit arrives in that input. Its name doesn't matter, but
#:package-path-inputs needs to point to its name.
> Another problem is that Cuirass crashes on startup. The Cuirass log
> shows me this:
>
> --8<---------------cut here---------------start------------->8---
> 2018-08-09T16:54:05 running Fibers on 4 kernel threads
> Uncaught exception in fiber ##f:
> In ice-9/eval.scm:
> 619:8 1 (_ #(#(#<directory (fibers) 127b500> #<<scheduler> ?> ?)))
> In unknown file:
> 0 (_ #<procedure 3de7aa0 at ice-9/eval.scm:330:13 ()> #<?> ?)
> ERROR: In procedure for-each: Wrong type argument: #f
> --8<---------------cut here---------------end--------------->8---
>
> The Cuirass process remains, but appears to be stuck.
This is because your specification list is invalid. I just noticed the
Guix manual about Cuirass is out of date. Please, have a look at the
Cuirass manual instead.
Clément
next prev parent reply other threads:[~2018-08-09 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 15:15 Cuirass fibers crash // using with GUIX_PACKAGE_PATH Ricardo Wurmus
2018-08-09 17:33 ` Clément Lassieur [this message]
2018-08-11 17:00 ` Ricardo Wurmus
2018-08-11 17:17 ` Clément Lassieur
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=87h8k3phqq.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=help-guix@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.
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).