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: Sat, 11 Aug 2018 19:17:41 +0200 [thread overview]
Message-ID: <877ekwrfey.fsf@lassieur.org> (raw)
In-Reply-To: <87r2j4bzy2.fsf@mdc-berlin.de>
Hi Ricardo,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>>> 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.
>
> Can we prevent this unhelpful error message by validating the
> specifications?
We definitely should, I opened https://bugs.gnu.org/32422 to keep track
of it.
Clément
prev parent reply other threads:[~2018-08-11 17:17 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
2018-08-11 17:00 ` Ricardo Wurmus
2018-08-11 17:17 ` Clément Lassieur [this message]
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=877ekwrfey.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).