GNU bug report logs -
#28484
Some steps and questions for Cuirass
Previous Next
Reported by: Jan Nieuwenhuizen <janneke <at> gnu.org>
Date: Sun, 17 Sep 2017 20:14:02 UTC
Severity: normal
Done: Jan Nieuwenhuizen <janneke <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #13 received at 28484-done <at> debbugs.gnu.org (full text, mbox):
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 <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ® http://AvatarAcademy.com
This bug report was last modified 7 years and 248 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.