From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia@riseup.net Subject: =?UTF-8?Q?Re=3A_hydra=2Egnu=2Eorg_now_provides_substitutes_for_?= =?UTF-8?Q?=E2=80=98guix_pull=E2=80=99?= Date: Tue, 26 Jun 2018 04:16:52 -0700 Message-ID: References: <87muvn1djp.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59547) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fXlxy-0004bY-EU for guix-devel@gnu.org; Tue, 26 Jun 2018 07:16:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fXlxu-0005Sr-F4 for guix-devel@gnu.org; Tue, 26 Jun 2018 07:16:58 -0400 In-Reply-To: <87muvn1djp.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org, ludo@gnu.org Cc: guix-sysadmin@gnu.org, clement@lassieur.org On June 22, 2018 9:32:58 AM GMT+02:00, ludo@gnu.org wrote:=20 > Hello Guix, >=20 > Yesterday Cl=C3=A9ment and I discussed on IRC what it would take for Hy= dra to > build build-aux/hydra/guix-modular.scm (i.e., the derivations that > correspond to 'guix pull'.) Cl=C3=A9ment rightly suggested that it was= a > matter of removing '--fresh-auto-compiled' from hydra-eval-guile-jobs=C2= =B9, > which I did, and it works: >=20 > https://hydra.gnu.org/jobset/guix/modular/ Fantastic! This really drastically cut the time to pull for me. Now the only thing that takes a toll is to compute the guix-derivation. Can we skip/workaround that too? Maybe we can deduce this from the build hydra already did? I'm guessing that the computation is needed to map a commit to a derivation that then maps to a build hydra has a substitute for. Hydra according to my understanding already did all this. Maybe we can communicate this to guix pull somehow? Example 1=20 I choose a commit that I know hydra has build e.g. 8edebd3 -> guix pull sees that this commit is already build and computed by hydra. -> guix pull fetches the resulting derivation and substitute and build only the locale profile stuff. Example 2 I simply run guix pull without knowing what hydra has done -> guix pull checks the latest commit to master -> checks if hydra has built it: no -> informs the user and gives them an option to choose a commit a few days back that hydra has built instead (saves time, power and is environmentally friendly :) ) -> based on the users choice moves forward. What do you think?