unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>, myglc2 <myglc2@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix infrastructure
Date: Sun, 09 Jul 2017 06:30:17 +0000	[thread overview]
Message-ID: <48ED86FB-61F3-4435-8B38-D68503422D78@flashner.co.il> (raw)
In-Reply-To: <20170707030042.GD1280@jasmine.lan>



On July 7, 2017 6:00:42 AM GMT+03:00, Leo Famulari <leo@famulari.name> wrote:
>On Thu, Jul 06, 2017 at 08:09:17PM -0400, myglc2 wrote:
>> On 07/01/2017 at 14:01 Leo Famulari writes:
>> > ... Bayfront is still not fully operational, so hydra.gnu.org is
>still
>> > serving as the front-end of the build farm. We are still relying on
>the
>> > Hydra software. That is, the situation is basically the same as
>before.
>> > Adding build machines will not help very much until the front-end
>> > hardware gets faster.
>> 
>> This leaves me wondering ...
>> 
>> Is the hydra/front-end hardware going to be upgraded?
>
>Yes...
>
>> Is bayfront/cuirass intended to replace hydra?
>
>... and yes.
>
>> The bayfront hardware described here ...
>> 
>> https://www.gnu.org/software/guix/news/growing-our-build-farm.html
>> 
>> ... seems weak to me. Is there a plan to scale it up and make it
>redundant?
>
>It will be a lot more powerful than the current Hydra system. As for
>specific plans, I'll let those administering the system chime in.
>
>> A reliable, resourced, managed, "nightly Guix build" should pay big
>> dividends for the project. But, from reading the lists, I get the
>> impression that such a thing does not exist. Is that correct?
>
>Currently, we tend to build all the packages as often as we can with
>our
>resources, which is less than once a day.
>
>> Do we know what would be needed to achieve a complete nightly build?
>
>It depends on what you mean by "complete".
>
>I doubt we can find armhf hardware that could build all the packages
>daily. That platform doesn't get very powerful in general and, in my
>experience, the machines that do exist can't handle sustained high
>loads, nor do they have fast network and I/O interfaces.
>
>It is possible for x86_64, i686, and eventually for aarch64. Maybe we
>will be able to cross-build from aarch64 to arhmf; I'm not sure.
>Efraim?

In theory it should be possible to build and run armhf packages on aarch64, in practice its not always the case. http://sjoerd.luon.net/posts/2017/07/debian-armhf-vm-on-arm64/ says:

On the 64 bit ARM side, we're running on Gigabyte MP30-AR1 based servers which can run 32 bit arm code (As opposed to e.g. ThunderX based servers which can only run 64 bit code). As such running armhf VMs on them to act as build slaves seems a good choice, but setting that up is a bit more involved than it might appear.


>
>Ricardo has been working on getting some new x86_64 / i686 builders
>online:
>
>https://gnunet.org/bot/log/guix/2017-06-30#T1433202

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

      parent reply	other threads:[~2017-07-09  6:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01 17:36 stability of master - just QA and hydra is not enough ng0
2017-07-01 18:01 ` Leo Famulari
2017-07-01 19:24   ` ng0
2017-07-01 19:52     ` Leo Famulari
2017-07-07  0:09   ` myglc2
2017-07-07  3:00     ` Guix infrastructure Leo Famulari
2017-07-07 12:19       ` Ludovic Courtès
2017-07-08 23:50         ` ng0
2017-07-09  9:21           ` Ricardo Wurmus
2017-07-09 12:06             ` Liam Wigney
2017-07-09 22:57               ` ng0
2017-07-09  0:43         ` myglc2
2017-07-09  8:49           ` Ricardo Wurmus
2017-07-11 18:44             ` Catonano
2017-07-09  6:30       ` Efraim Flashner [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

  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=48ED86FB-61F3-4435-8B38-D68503422D78@flashner.co.il \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=myglc2@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 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).