From: "Karl G. Hallsby" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 65606@debbugs.gnu.org
Subject: bug#65606: Cuirass Compute Guix Derivation Bug
Date: Wed, 22 Nov 2023 22:39:40 -0600 [thread overview]
Message-ID: <87leapgjrf.fsf@hallsby.com> (raw)
In-Reply-To: <87a5r5853f.fsf@gmail.com>
> The problem occurred while downloading a substitute, so it seems to be a
> bug in 'guix substitute'. Perhaps related to a network problem that was
> not correctly handled.
That might be it. I have completely forgotten what this submission was
about or how I hit it. The only other pieces of information I can
provide is that Cuirass instance is running in a VM on Proxmox and that
I am using the default build mode with the local daemon. This machine is
CI for my personal projects and channels, so a single machine is enough
for building those.
I think this was a transient issue. Doing a "herd restart cuirass" fixed
it, I think.
I have not seen this issue again, though I have seen others with
Cuirass. These new issues do not belong in this thread though.
> The backtrace is not super useful... I wonder how we could change
> that.
Getting better backtraces for Cuirass-issued Guix commands would be
amazing! There are some instances, like this one, where the backtrace
does not help much.
--
Raven Hallsby
prev parent reply other threads:[~2023-11-23 4:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 1:12 bug#65606: Cuirass Compute Guix Derivation Bug Karl G. Hallsby via Bug reports for GNU Guix
2023-11-23 4:29 ` Maxim Cournoyer
2023-11-23 4:39 ` Karl G. Hallsby via Bug reports for GNU Guix [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87leapgjrf.fsf@hallsby.com \
--to=bug-guix@gnu.org \
--cc=65606@debbugs.gnu.org \
--cc=karl@hallsby.com \
--cc=maxim.cournoyer@gmail.com \
/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.