Hi,
Sorry for the late reply.
On mer., 20 déc. 2023 at 14:02, Aleksandr Vityazev wrote:
> Is it possible to make the build continue locally after several
> unsuccessful attempts?
That’s a feature I also would like. :-) Some pointers for the
interested reader:
bug#24496: offloading should
On 2023-12-20 17:19, Saku Laesvuori wrote:
>> Hello.
>>
>> I have a configured build machine. From time to time it is not available
>> and guix build gets stuck in an endless loop of:
>>
>> guix offload: error: failed to connect to : No route to host
>> process 13902 acquired build slot
>> guix
> Hello.
>
> I have a configured build machine. From time to time it is not available
> and guix build gets stuck in an endless loop of:
>
> guix offload: error: failed to connect to : No route to host
> process 13902 acquired build slot
> guix offload: error: failed to connect to : No route to
On 2023-12-20 13:29, Reza Housseini wrote:
> On 12/20/23 12:02, Aleksandr Vityazev wrote:
>> Hello.
>> I have a configured build machine. From time to time it is not
>> available
>> and guix build gets stuck in an endless loop of:
>> guix offload: error: failed to connect to : No route to host
>>
On 12/20/23 12:02, Aleksandr Vityazev wrote:
Hello.
I have a configured build machine. From time to time it is not available
and guix build gets stuck in an endless loop of:
guix offload: error: failed to connect to : No route to host
process 13902 acquired build slot
guix offload: error: faile
Hallå
No. Not yet at least. See http://lists.gnu.org/archive/
> html/guix-devel/2018-06/msg00316.html where I also proposed a change to
> guix pull which makes it do the least cpu intensive update by default.
>
Interesting. So how do you find a commit that have the least cpu intensive
update?
20
Hej 😀
On June 28, 2018 6:36:57 PM GMT+02:00, Fredrik Salomonsson
wrote:
>Hi
>
>1) the new possibility of picking a commit that hydra already built
>thus
>> avoiding the compilation of guix locally?
>
>Didn't know that. Is that some sort of combination with "guix weather"
>and
>"guix pull --commi
Hi
1) the new possibility of picking a commit that hydra already built thus
> avoiding the compilation of guix locally?
Didn't know that. Is that some sort of combination with "guix weather" and
"guix pull --commit"?
> 2) the ability to control the cpu frequency via a governor or the program
>
On June 28, 2018 8:09:14 AM GMT+02:00, Fredrik Salomonsson
wrote:
>Hi,
>
>got inspired by this thread to try and setup offloading for my laptop.
>As
>everytime I run guix pull my laptop sounds like it's preparing to take
>off.
>
Hi.
Are you aware of
1) the new possibility of picking a commit
Hi,
got inspired by this thread to try and setup offloading for my laptop. As
everytime I run guix pull my laptop sounds like it's preparing to take off.
But running into problems similar to what Matthew described. I.e. it just
get stuck.
> $ guix offload test
>
guix offload: testing 1 build mac
It seems to be working now, for some reason.
I updated guix in the user and root accounts on the build machine again, and
double-checked the .bashrc configs since one of them said I needed to add
".config/guix/current/bin" to the path (even though I swear I did that the
other day, but it wasn't
Hi Ludo',
on [2017-03-06] at 10:52 Ludovic Courtès writes:
> Myles English skribis:
>
>> Two hosts, setup the same as far as I can see, behave differently when
>> trying to offload builds, any idea how I can get more information on
>> what the # might indicate? Looking at
>> guix/scripts/offloa
Hi Myles,
Myles English skribis:
> Two hosts, setup the same as far as I can see, behave differently when
> trying to offload builds, any idea how I can get more information on
> what the # might indicate? Looking at
> guix/scripts/offload.scm:551 suggests the result is not a string.
>
> $ guix
13 matches
Mail list logo
