From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 43905@debbugs.gnu.org
Subject: bug#43905: Acknowledgement (cuirass: uncaught exception 'read-error' in 'metrics' fiber)
Date: Mon, 2 Nov 2020 19:19:58 +0100 [thread overview]
Message-ID: <1216ca5e-f9ab-e9ce-0117-5c0228a791aa@web.de> (raw)
In-Reply-To: <87tuuzrj1k.fsf@gnu.org>
On 12.10.20 09:37, Mathieu Othacehe wrote:
>
> Hello Jonathan,
>
>> It happens when scamping around in the database:
>> update Specifications set proc_args='((subset "htop" "icedove") (systems
>> "x86_64-linux))';
>
> You mean it happens only when modifying 'proc_args' while Cuirass is
> running? Could you share your specifications so that I can try to
> reproduce it?
Sorry for the late answer
```
(define %cuirass-specs
#~(list
'((#:name . "foo-master")
(#:load-path-inputs . ())
(#:package-path-inputs . ("foo-packages"))
(#:proc-input . "guix")
(#:proc-file . "build-aux/cuirass/gnu-system.scm")
(#:proc . cuirass-jobs)
(#:proc-args . ((subset . ("htop" "icedove"))
(systems . ("x86_64-linux"))))
(#:inputs . (((#:name . "guix")
(#:url . "https://git.savannah.gnu.org/git/guix.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t))
((#:name . "foo-packages")
(#:url . "https://gitlab.com/foo/foo.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t))))
(#:build-outputs . ()))))
```
next prev parent reply other threads:[~2020-11-02 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 10:02 bug#43905: cuirass: uncaught exception 'read-error' in 'metrics' fiber Jonathan Brielmaier
[not found] ` <handler.43905.B.160232418120408.ack@debbugs.gnu.org>
2020-10-11 17:39 ` bug#43905: Acknowledgement (cuirass: uncaught exception 'read-error' in 'metrics' fiber) Jonathan Brielmaier
2020-10-12 7:37 ` Mathieu Othacehe
2020-11-02 18:19 ` Jonathan Brielmaier [this message]
2021-03-25 12:50 ` bug#43905: cuirass: uncaught exception 'read-error' in 'metrics' fiber Mathieu Othacehe
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=1216ca5e-f9ab-e9ce-0117-5c0228a791aa@web.de \
--to=jonathan.brielmaier@web.de \
--cc=43905@debbugs.gnu.org \
--cc=othacehe@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).