all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: cuirass evaluate
Date: Tue, 25 Jul 2017 23:27:25 +0200	[thread overview]
Message-ID: <87k22wb41u.fsf@gnu.org> (raw)
In-Reply-To: <86y3rj2mj1.fsf@gmail.com> (Mathieu Othacehe's message of "Thu, 20 Jul 2017 16:47:14 +0200")

Hello,

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

>> 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.

Sounds good.  Let us know if you stumble upon other issues.

Thanks,
Ludo.’

      reply	other threads:[~2017-07-25 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-08  9:15 cuirass evaluate Mathieu Othacehe
2017-07-10 15:12 ` Ludovic Courtès
2017-07-11 17:17   ` Mathieu Othacehe
2017-07-12  9:39     ` Mathieu Othacehe
2017-07-17 13:32       ` Ludovic Courtès
2017-07-20 14:47         ` Mathieu Othacehe
2017-07-25 21:27           ` Ludovic Courtès [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k22wb41u.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@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 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.