From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: help-guix@gnu.org
Subject: Cuirass fibers crash // using with GUIX_PACKAGE_PATH
Date: Thu, 9 Aug 2018 17:15:14 +0200 [thread overview]
Message-ID: <idjwosz7erh.fsf@bimsb-sys02.mdc-berlin.net> (raw)
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?
Previously I set up a cron job to update the second repository and
added it on the load-path through the Cuirass service configuration.
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?
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.
--
Ricardo
next reply other threads:[~2018-08-09 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 15:15 Ricardo Wurmus [this message]
2018-08-09 17:33 ` Cuirass fibers crash // using with GUIX_PACKAGE_PATH Clément Lassieur
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=idjwosz7erh.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=help-guix@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 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.