offloading does not transfer build logs

OpenSubmitted by ng0.
Details
2 participants
  • Ludovic Courtès
  • ng0
Owner
unassigned
Severity
normal
N
(address . bug-guix@gnu.org)
20170825144220.xk6wuf2ryokvbgqi@abyayala
Short and simple, currently we have this, assuming thatyou have first build mutt on a different machine via offloadingbuilds afterwards produce this:
guix build --no-build-hook --log-file muttguix build: error: no build log for '/gnu/store/zmx9c4akha95l13c5066phgm6vgdbbf9-mutt-1.8.3.drv'
Expected behavior would be that you get the location of thebuild log.-- ng0GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588GnuPG: https://n0is.noblogs.org/my-keyshttps://www.infotropique.orghttps://krosos.org
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmgN0wACgkQ4i+bv+40hYi0mBAAtiImY275HtRZjEGIjdDWdmhH+x8oCxVn+rW/ERaXohx83WeX5pl5yYMJYQ7BSscgvdKx9UDmS5o7cUH93FCLMUrJ0neJ1cQllfImm6HPPcdSui7j91vuc12cham72mcJIIv3Iy+aStQsPsmnT8iHHXtKePRoNaDy2FlpJ4Q+oeFjTIJSCoSsnelTuwJvuYidF9Qk5X7aoiG20NjtvQfEO9nx1sATFbaggFS/7TRhjvQ4G0+JnfobRS1592FnF332LVKjDApJ6MzYAjerNxuy0PJ56ae/BNKgAO13QeUPYWjaBQitmpOcWt74+/lgwEPSSGwm+srdLtf9/sTQhVnaO2VFG2om/n2RCzwa8/e3JfOVIMTo/lteNWQLlnOU4N+kUlCCJ6IbIHPuoaXkZ53EfikZ75fLM5hvvOK2ARQi21lBlDHnoJYE7EkgEPCAZdbxV0v1s+SRxarJssuFIbMXlztiAVsfl3anC3v1INiikDaIgdvp1OzhTmtMnB6yLJxAjgtvq8JBcli5G9ttGuj2U/HIe/mFyzIABkYymN7N8cmN9H/Ds69Ohz4aQYzf+WM3z6ypk+rw9Lb5w7A21c8J2aw2aBEHWEGHIT8jtzXd2RV3opJ9y4f7tzaadjRovWVHD6g8g6Pzo0jwmsyMYH08Jnnnc//Mv2Vp7Sgjoe7KlEw==jyyW-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 25 Aug 2017 22:43
(name . ng0)(address . ng0@infotropique.org)(address . 28230@debbugs.gnu.org)
87tw0ve5ub.fsf@gnu.org
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 logof 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 masternode ends up with the build log as it if were built locally.
There’s one exception though: if the thing that was offloaded wasactually already available in the build machine’s store, then the masternode won’t get any build log. Perhaps that’s what happened?
HTH,Ludo’.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send email to 28230@debbugs.gnu.org