From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] hydra: Use the new 'systems' field for build-machine definitions.
Date: Sun, 30 Aug 2020 23:06:36 -0400 [thread overview]
Message-ID: <87mu2bsedf.fsf@gmail.com> (raw)
In-Reply-To: <87imd3l1ez.fsf@gnu.org> (Mathieu Othacehe's message of "Fri, 28 Aug 2020 08:39:16 +0200")
Hello Mathieu,
Mathieu Othacehe <othacehe@gnu.org> writes:
> Hello Maxim,
>
>> (fast/hurd (filter (compose childhurd-ip? build-machine-name) fast)))
>> (append overdrive (map aarch64->armhf overdrive)
>> armv7
>> - x86_64 (map x86_64->i686 x86_64)
>> + x86_64
>> (map x86_64->qemu-aarch64 fast)
>> (map x86_64->qemu-armhf fast)
>> (map x86_64->childhurd fast/hurd)))
>
> You could also get rid of "x86_64->qemu-aarch64" and
> "x86_64->qemu-armhf" adding:
The reason I've kept those in is that they are used to dial the speed
field of the emulated build machines down, to prefer native hardware.
I'm not sure if this is still useful / worth the additional complexity?
> (define template-x86_64
> (match-lambda
> ;; Prefer building on the new nodes.
> ((name key 128)
> (build-machine
> (name name)
> (user "hydra")
> (systems ("x86_64-linux" "i686-linux"
> "aarch64-linux" "armhf-linux"))
> (host-key key)
> (compression "no")
>
> Otherwise, this looks good :)
Thanks! I don't have SSH access to these machines, but it'll be
necessary to reconfigure them before updating those files.
Maxim
next prev parent reply other threads:[~2020-08-31 3:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 4:02 [PATCH] hydra: Use the new 'systems' field for build-machine definitions Maxim Cournoyer
2020-08-28 6:39 ` Mathieu Othacehe
2020-08-31 3:06 ` Maxim Cournoyer [this message]
2020-09-03 5:31 ` Mathieu Othacehe
2020-09-07 19:29 ` Maxim Cournoyer
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=87mu2bsedf.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@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).