From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mathieu Othacehe <m.othacehe@gmail.com>
Subject: Re: cuirass evaluate
Date: Thu, 20 Jul 2017 16:47:14 +0200
Message-ID: <86y3rj2mj1.fsf@gmail.com>
References: <87podbthkk.fsf@gmail.com> <87k23g498e.fsf@gnu.org>
	<87o9squc3d.fsf@gmail.com> <86eftmm1sx.fsf@gmail.com>
	<878tjn89z9.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47612)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.othacehe@gmail.com>) id 1dYCjW-0005YX-I1
	for guix-devel@gnu.org; Thu, 20 Jul 2017 10:47:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <m.othacehe@gmail.com>) id 1dYCjS-00043e-Jq
	for guix-devel@gnu.org; Thu, 20 Jul 2017 10:47:18 -0400
In-reply-to: <878tjn89z9.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>


Hi Ludo,

> Unfortunately, the current daemon protocol makes it hard to get such
> notifications, unless you parse its output (the “@ build-succeeded”
> lines) like I did in ‘wip-ui’.
>
> Perhaps we’ll have to do this parsing anyway, or just change the
> protocol altogether and have a “channel” mechanism like SSH to multiplex
> the number of communication channels on one connection.  reepca, if you
> read this, that’s something to keep in mind.  :-)
>
> Alternately, Cuirass could also periodically call ‘valid-path?’ for all
> the outputs of the pending builds (in a separate thread; note that the
> daemon connection cannot be shared among threads.)

Ok, the solution you implemented in wip-ui seems viable.

For now I'm implementing basic web API in cuirass :

* api/build/:build
* build/:build/log/raw
* api/latestbuilds

This allows emacs-guix to query cuirass as per hydra. The "queue" api
will be implementable when we will support build start/stop/failure
detection.

Thanks,

Mathieu