bug#28230: offloading does not transfer build logs

bug#28230: offloading does not transfer build logs

[ng0]

[-- Attachment #1: Type: text/plain, Size: 523 bytes --]

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/zmx9c4akha95l13c5066phgm6vgdbbf9-mutt-1.8.3.drv'

Expected behavior would be that you get the location of the
build log.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#28230: offloading does not transfer build logs

[Ludovic Courtès]

Hi,

ng0 <ng0@infotropique.org> 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/zmx9c4akha95l13c5066phgm6vgdbbf9-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’re asking for the log
of the grafting derivation.

Apart from that, offloading does “transfer” logs to the master node
(search for ‘build-log-port’ in (guix scripts offload)).  So the master
node ends up with the build log as it if were built locally.

There’s one exception though: if the thing that was offloaded was
actually already available in the build machine’s store, then the master
node won’t get any build log.  Perhaps that’s what happened?

HTH,
Ludo’.