From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/04: gnu: mesa: Disable imx driver for armhf-linux.
Date: Mon, 16 Oct 2017 17:52:50 -0400 [thread overview]
Message-ID: <20171016215250.GD20802@jasmine.lan> (raw)
In-Reply-To: <874lqzfdyx.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On Mon, Oct 16, 2017 at 02:56:38PM +0200, Ludovic Courtès wrote:
> From the maintainer’s viewpoint, it just stresses that we must keep
> going with the efforts to improve our build infrastructure. Currently
> that has only benefited x86, but perhaps now is a good time to plug our
> ARM boxes behind berlin.guixsd.org, for a start.
>
> Thoughts?
What sort of interface do we have for querying berlin.guixsd.org's
evalutions (to borrow the Hydra term)?
Is it just `guix weather`, or is there some sort of historical
continuous integration view as with the Hydra interface?
For all the frustrations with Hydra, it's still invaluable to be able to
compare evaluations and look at things like "newly failing jobs", and to
share hyperlinks with each other.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-16 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171012173828.26257.23460@vcs0.savannah.gnu.org>
[not found] ` <20171012173830.72AE320339@vcs0.savannah.gnu.org>
2017-10-13 1:06 ` 01/04: gnu: mesa: Disable imx driver for armhf-linux Mark H Weaver
2017-10-13 14:58 ` Marius Bakke
2017-10-13 16:57 ` Mark H Weaver
2017-10-14 0:38 ` Mark H Weaver
2017-10-14 10:30 ` Marius Bakke
2017-10-16 12:56 ` Ludovic Courtès
2017-10-16 21:52 ` Leo Famulari [this message]
2017-10-17 16:08 ` Cuirass HTTP API Ludovic Courtès
2017-10-17 19:49 ` Ricardo Wurmus
2017-10-14 17:51 ` 01/04: gnu: mesa: Disable imx driver for armhf-linux Leo Famulari
2017-10-18 13:53 ` Ricardo Wurmus
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=20171016215250.GD20802@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.