From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45533) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtubr-000795-SN for guix-patches@gnu.org; Mon, 18 Sep 2017 07:53:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dtubm-0004Em-Vn for guix-patches@gnu.org; Mon, 18 Sep 2017 07:53:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:36933) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dtubm-0004EG-S9 for guix-patches@gnu.org; Mon, 18 Sep 2017 07:53:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dtubm-0007Ng-I5 for guix-patches@gnu.org; Mon, 18 Sep 2017 07:53:02 -0400 Subject: [bug#28484] Some steps and questions for Cuirass Resent-Message-ID: References: <20170917201157.9802-1-janneke@gnu.org> From: Mathieu Othacehe In-reply-to: <20170917201157.9802-1-janneke@gnu.org> Date: Mon, 18 Sep 2017 13:51:58 +0200 Message-ID: <86y3pci5r5.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Jan Nieuwenhuizen Cc: 28484@debbugs.gnu.org Hi Jan, > ...although that may be a feature? I don't think so, patch 1 & 2 LGTM. > Patch 3/3 is the one I'm least happy with. When building many more packages > than only `hello', Cuirass will not give any feedback until after everything > is built. The Emacs interface under M-x guix-hydra-latests-builds is very > nice, but polling for that less so. > > As the comment in the file already says > > ;; Register the results in the database. > ;; XXX: The 'build-derivations' call is blocking so we end updating the > ;; database potentially long after things have been built. > > we probably want feedback (or guix-hydra-latests-builds availability) per > package...but any ideas how to do that? We'd have to wrap/closure that into > building the derivations? 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. Until this is developed, patch 3 LGTM too ! Mathieu