From: "Collin J. Doering" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 68237@debbugs.gnu.org
Subject: bug#68237: Cuirass 1.2.0-1.bdc1f9f local builds never occur
Date: Wed, 03 Jan 2024 21:39:02 -0500 [thread overview]
Message-ID: <87mstl4wrc.fsf@rekahsoft.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
After updating cuirass (details below), my cuirass instance no longer builds anything! It continues to poll channels, run evaluations and queue builds, but none of the builds ever run.
--8<---------------cut here---------------start------------->8---
Before: Cuirass 1.1.0-13.1341725 (guix checkout c4cca9cb5d3e93ef146acb930a95da9d2da6fb06)
After: Cuirass 1.2.0-1.bdc1f9f (guix checkout 25b83bd9e4ceb77f08c0caee3ecdc48263b53a46)
--8<---------------cut here---------------end--------------->8---
After a bit of investigation, I noticed numerous instances of this in the logs following the update:
--8<---------------cut here---------------start------------->8---
/var/log/guix-daemon.log-2024-01-03 10:08:22 SIGPOLL
/var/log/guix-daemon.log:2024-01-03 10:08:22 unexpected build daemon error: interrupted by the user
--8<---------------cut here---------------end--------------->8---
It may be worth noting that I am running cuirass with substitutes on.
Any help appreciated.
--
Collin J. Doering
http://rekahsoft.ca
http://blog.rekahsoft.ca
http://git.rekahsoft.ca
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]
next reply other threads:[~2024-01-04 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 2:39 Collin J. Doering via Bug reports for GNU Guix [this message]
2024-01-08 16:44 ` bug#68237: Cuirass 1.2.0-1.bdc1f9f local builds never occur Haugen, Kjetil via Bug reports for GNU Guix
2024-01-09 17:42 ` Ludovic Courtès
2024-01-15 9:40 ` Ludovic Courtès
2024-01-15 18:49 ` Haugen, Kjetil via Bug reports for GNU Guix
2024-01-15 22:31 ` Collin J. Doering via Bug reports for GNU Guix
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=87mstl4wrc.fsf@rekahsoft.ca \
--to=bug-guix@gnu.org \
--cc=68237@debbugs.gnu.org \
--cc=collin@rekahsoft.ca \
/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).