Hi,
Maxim Cournoyer skribis:
> I just reviewed this commit, and don't see anywhere where the behavior
> would have changed. The discarding happens here:
>
> - (if (and node (< load 2.) (>= space %minimum-disk-space))
> + (if (and node
> + (or (not threshold) (<
Hi,
I have not checked all the details, since the code of “guix offload” is
run by root, IIUC and so it is not as friendly as usual to debug. :-)
On Fri, 17 Dec 2021 at 16:57, Maxim Cournoyer wrote:
>> However, I think this behavior was unintentionally lost in
>>
Hello Ludovic,
Ludovic Courtès writes:
> Hi!
>
> zimoun skribis:
>
>> I am just hitting this old bug#24496 [1].
>>
>> On Mon, 26 Sep 2016 at 18:20, l...@gnu.org (Ludovic Courtès) wrote:
>>> ng0 skribis:
>>>
When I forgot that my build machine is offline and I did not pass
Hi!
zimoun skribis:
> I am just hitting this old bug#24496 [1].
>
> On Mon, 26 Sep 2016 at 18:20, l...@gnu.org (Ludovic Courtès) wrote:
>> ng0 skribis:
>>
>>> When I forgot that my build machine is offline and I did not pass
>>> --no-build-hook, the offloading keeps trying forever until I had
Hi,
I am just hitting this old bug#24496 [1].
On Mon, 26 Sep 2016 at 18:20, l...@gnu.org (Ludovic Courtès) wrote:
> ng0 skribis:
>
>> When I forgot that my build machine is offline and I did not pass
>> --no-build-hook, the offloading keeps trying forever until I had to
>> cancel the build,
Ludovic Courtès writes:
> Hello!
>
> ng0 skribis:
>
>> When I forgot that my build machine is offline and I did not pass
>> --no-build-hook, the offloading keeps trying forever until I had to
>> cancel the build, boot the build-machine and started the build
Hello!
ng0 skribis:
> When I forgot that my build machine is offline and I did not pass
> --no-build-hook, the offloading keeps trying forever until I had to
> cancel the build, boot the build-machine and started the build again.
>
> A solution could be a config option or
When I forgot that my build machine is offline and I did not pass
--no-build-hook, the offloading keeps trying forever until I had to
cancel the build, boot the build-machine and started the build again.
A solution could be a config option or default behavior which after
failing to offload for n