From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#28230: offloading does not transfer build logs Date: Fri, 25 Aug 2017 22:43:24 +0200 Message-ID: <87tw0ve5ub.fsf@gnu.org> References: <20170825144220.xk6wuf2ryokvbgqi@abyayala> 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]:48527) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dlLSY-0002bX-8p for bug-guix@gnu.org; Fri, 25 Aug 2017 16:44:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dlLSV-00008L-72 for bug-guix@gnu.org; Fri, 25 Aug 2017 16:44:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:46433) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dlLSV-00008C-3Q for bug-guix@gnu.org; Fri, 25 Aug 2017 16:44:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dlLSU-0004pZ-U7 for bug-guix@gnu.org; Fri, 25 Aug 2017 16:44:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20170825144220.xk6wuf2ryokvbgqi@abyayala> (ng0@infotropique.org's message of "Fri, 25 Aug 2017 14:42:20 +0000") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: ng0 Cc: 28230@debbugs.gnu.org Hi, ng0 skribis: > Short and simple, currently we have this, assuming that > you have first build mutt on a different machine via offloading > builds afterwards produce this: > > guix build --no-build-hook --log-file mutt > guix build: error: no build log for '/gnu/store/zmx9c4akha95l13c5066phgm6= vgdbbf9-mutt-1.8.3.drv' > > Expected behavior would be that you get the location of the > build log. Note that you may need --no-grafts, otherwise you=E2=80=99re asking for the= log of the grafting derivation. Apart from that, offloading does =E2=80=9Ctransfer=E2=80=9D logs to the mas= ter node (search for =E2=80=98build-log-port=E2=80=99 in (guix scripts offload)). S= o the master node ends up with the build log as it if were built locally. There=E2=80=99s one exception though: if the thing that was offloaded was actually already available in the build machine=E2=80=99s store, then the m= aster node won=E2=80=99t get any build log. Perhaps that=E2=80=99s what happened? HTH, Ludo=E2=80=99.