From: Christopher Baines <mail@cbaines.net>
To: Joshua Branson <jbranso@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Getting the Guix Build Coordinator agent working on the Hurd
Date: Tue, 16 Feb 2021 08:58:30 +0000 [thread overview]
Message-ID: <87ft1wfky1.fsf@cbaines.net> (raw)
In-Reply-To: <87a6s5mkk8.fsf@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Joshua Branson <jbranso@dismail.de> writes:
> Christopher Baines <mail@cbaines.net> writes:
>
>> Hey,
>>
>> This has been on my todo list ever since the childhurd service came in
>> to existence. I spent some more time looking at it yesterday, and did
>> manage to get the agent working in a childhurd VM, at least somewhat.
>
> Firstly awesome!
Thanks!
>> There's also one problem probably within the Guix Build Coordinator
>> itself, after doing a few builds, it will just stop. I've only seen this
>> behaviour on the Hurd, but I'm unsure how to debug it, any suggestions?
>> My only idea is add more logging.
>
> You could always email bug-hurd@gnu.org or hang out in the #hurd
> channel. Samuel is pretty quick to reply. He's about as responsive as
> Ludo!
I disabled some features, and that seemed to help, so maybe I'll try to
come up with a small reproducer which hangs next [1].
1: https://git.cbaines.net/guix/build-coordinator/commit/guix-build-coordinator?id=b3733bca21de607fd7a70319e66e3ff49996a974
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2021-02-16 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 11:39 Getting the Guix Build Coordinator agent working on the Hurd Christopher Baines
2021-02-15 15:12 ` Joshua Branson
2021-02-16 8:58 ` Christopher Baines [this message]
2021-02-16 8:57 ` Christopher Baines
2021-02-18 9:25 ` Christopher Baines
2021-02-18 17:35 ` Ludovic Courtès
2021-02-23 20:58 ` Christopher Baines
2021-03-10 10:10 ` Ludovic Courtès
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=87ft1wfky1.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=jbranso@dismail.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.
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.