unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 28484-done@debbugs.gnu.org
Subject: bug#28484: Some steps and questions for Cuirass
Date: Mon, 18 Sep 2017 17:44:08 +0200	[thread overview]
Message-ID: <87shfk2erb.fsf@gnu.org> (raw)
In-Reply-To: <86y3pci5r5.fsf@gmail.com> (Mathieu Othacehe's message of "Mon, 18 Sep 2017 13:51:58 +0200")

Mathieu Othacehe writes:

> I don't think so, patch 1 & 2 LGTM.

Thanks!

> Now that Cuirass supports M-x guix-hydra-latests-builds, the next step
> is to detect build start/stop (maybe via guix build log parsing see:
> https://lists.gnu.org/archive/html/guix-devel/2017-07/msg00221.html).
>
> This way, for each new commit in guix, cuirass will only insert in
> database the derivation that were built. Plus, it will be possible to
> insert the build in db when it starts and update its status when it
> stops/fails.

Ah that makes sense.  Thanks for sharing this thread.

> Until this is developed, patch 3 LGTM too !

Thanks, pushed to guix-cuirass master as 87ad259dba7de38b6e3ab954cd7b2f655358d877

janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

      reply	other threads:[~2017-09-18 15:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17 20:11 [bug#28484] Some steps and questions for Cuirass Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28485] [PATCH 1/3] base: Make working copy writable Jan Nieuwenhuizen
     [not found]   ` <handler.28485.B.1505679193775.ack@debbugs.gnu.org>
2017-09-18 15:46     ` bug#28485: Acknowledgement ([PATCH 1/3] base: Make working copy writable.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28486] [PATCH 2/3] gnu-system: Accept subset with list of package names Jan Nieuwenhuizen
     [not found]   ` <handler.28486.B.1505679194784.ack@debbugs.gnu.org>
2017-09-18 15:45     ` bug#28486: Acknowledgement ([PATCH 2/3] gnu-system: Accept subset with list of package names.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28488] [PATCH 3/3] base: Show feedback when build has finished Jan Nieuwenhuizen
     [not found]   ` <handler.28488.B.1505679198802.ack@debbugs.gnu.org>
2017-09-18 15:48     ` bug#28488: Acknowledgement ([PATCH 3/3] base: Show feedback when build has finished.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28487] [PATCH] cuirass: Add gnu-system build spec Jan Nieuwenhuizen
2017-09-26  8:18   ` Ludovic Courtès
2017-09-26 17:56     ` Jan Nieuwenhuizen
2017-09-26 18:05       ` Jan Nieuwenhuizen
2017-09-26 20:29       ` Ludovic Courtès
2017-09-27 18:55         ` Jan Nieuwenhuizen
2017-09-27 19:45           ` Ludovic Courtès
2017-09-27 20:32             ` Jan Nieuwenhuizen
2017-09-27 20:52               ` Jan Nieuwenhuizen
2017-09-28  8:26                 ` Ludovic Courtès
2017-09-28 15:41                   ` bug#28487: " Jan Nieuwenhuizen
2017-09-28  8:27               ` [bug#28487] " Ludovic Courtès
2017-09-28 16:04                 ` Jan Nieuwenhuizen
2017-09-18 11:51 ` [bug#28484] Some steps and questions for Cuirass Mathieu Othacehe
2017-09-18 15:44   ` Jan Nieuwenhuizen [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=87shfk2erb.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=28484-done@debbugs.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 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).