Hi Maxim, Maxim Cournoyer <[email protected]> skribis:
> Sometimes 'guix deploy' ends up failing near the end, with what looks > like: > > guix deploy: sending 180 store items (1,094 MiB) to 'myhost'... > [...] (progress bar) > guix deploy: error: failed to deploy mymachine: failed to start Guile on > remote host 'myhost' > > > Upon retrying the same 'guix deploy' command, it usually succeeds, e.g.: > > guix deploy: sending 8 store items (5 MiB) to 'myhost'... > guix deploy: successfully deployed mymachine I’ve seen it too, and I think it might be the same issue as described here: https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=cdef930632d0a94b0d92bf4f5fc7227e75c6eb10 If that happens again, could you log in the target machine as root and run: find ~/.cache/guile | xargs ls -lrtd That way you’ll see if some .go files have just been compiled, and also if there are temporary .go.XYZ files in there (stemming from an interrupted compilation process due to the timeout.) Thanks, Ludo’.
