offloading does not transfer build logs

  • Open
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • ng0
Owner
unassigned
Submitted by
ng0
Severity
normal
N
N
ng0 wrote on 25 Aug 2017 16:42
Download
(address . bug-guix@gnu.org)
20170825144220.xk6wuf2ryokvbgqi@abyayala
Download
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
Download
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmgN0wACgkQ4i+bv+40
hYi0mBAAtiImY275HtRZjEGIjdDWdmhH+x8oCxVn+rW/ERaXohx83WeX5pl5yYMJ
YQ7BSscgvdKx9UDmS5o7cUH93FCLMUrJ0neJ1cQllfImm6HPPcdSui7j91vuc12c
ham72mcJIIv3Iy+aStQsPsmnT8iHHXtKePRoNaDy2FlpJ4Q+oeFjTIJSCoSsnelT
uwJvuYidF9Qk5X7aoiG20NjtvQfEO9nx1sATFbaggFS/7TRhjvQ4G0+JnfobRS15
92FnF332LVKjDApJ6MzYAjerNxuy0PJ56ae/BNKgAO13QeUPYWjaBQitmpOcWt74
+/lgwEPSSGwm+srdLtf9/sTQhVnaO2VFG2om/n2RCzwa8/e3JfOVIMTo/lteNWQL
lnOU4N+kUlCCJ6IbIHPuoaXkZ53EfikZ75fLM5hvvOK2ARQi21lBlDHnoJYE7Ekg
EPCAZdbxV0v1s+SRxarJssuFIbMXlztiAVsfl3anC3v1INiikDaIgdvp1OzhTmtM
nB6yLJxAjgtvq8JBcli5G9ttGuj2U/HIe/mFyzIABkYymN7N8cmN9H/Ds69Ohz4a
QYzf+WM3z6ypk+rw9Lb5w7A21c8J2aw2aBEHWEGHIT8jtzXd2RV3opJ9y4f7tzaa
djRovWVHD6g8g6Pzo0jwmsyMYH08Jnnnc//Mv2Vp7Sgjoe7KlEw=
=jyyW
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 25 Aug 2017 22:43
Download
(name . ng0)(address . ng0@infotropique.org)(address . 28230@debbugs.gnu.org)
87tw0ve5ub.fsf@gnu.org
Download
Hi,

ng0 <ng0@infotropique.org> skribis:

Toggle quote (10 lines)
> 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’.
?