From: myglc2 <myglc2@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: stability of master - just QA and hydra is not enough
Date: Thu, 06 Jul 2017 20:09:17 -0400 [thread overview]
Message-ID: <86d19dxg42.fsf@gmail.com> (raw)
In-Reply-To: <20170701180111.GA29205@jasmine.lan> (Leo Famulari's message of "Sat, 1 Jul 2017 14:01:11 -0400")
On 07/01/2017 at 14:01 Leo Famulari writes:
> On Sat, Jul 01, 2017 at 05:36:04PM +0000, ng0 wrote:
[...]
>> 0: What is it these days? Is hydra now just a in-retirement frontend
>> for cuirass or how does bayfront work these days? I understand cuirass,
>> not hydra.
>
> ... 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?
Is bayfront/cuirass intended to replace hydra?
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?
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?
Do we know what would be needed to achieve a complete nightly build?
TIA - George
next prev parent reply other threads:[~2017-07-07 0:09 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 [this message]
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
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=86d19dxg42.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).