Hi Ludovic,
Ludovic Courtès <l...@gnu.org> writes:
> I suppose the only way to solve this correctly would be to keep the
> build tree and then delete it from (guix scripts offload). WDYT?
Generally, this sounds like a reasonable approach. However, one issue
is that it will likely lead to build directories being left around
occasionally when transient network outages occur. Those would need to
be cleaned up manually, or by cron jobs on the build slaves.
Also, does the daemon API provide a way to find the name of the build
directory? What if there's more than one build directory with the same
name and version number, differing only by the numeric suffix?
Ideally, there would be a way for the build-side code to return a result
code indicating that the build "aborted" rather than "failed", for this
to be recognized by the daemon as a transient failure (i.e. not cached),
and to propagate this information back to the client who requested the
build. Do the relevant daemon APIs and offloading protocols allow for
this information to be propagated to the client?
Thanks,
Mark
