bug#55848: [cuirass] workers stalled

Hi, Ricardo Wurmus skribis: > Ludovic Courtès writes: > >> Ludovic Courtès skribis: >> >>> guix-daemon is configured to use the default substitute URLs, >>> https://ci.guix.gnu.org and https://bordeaux.guix.gnu.org, which we know >>> are unreachable. >>> >>> I’ve theoretically addressed this

bug#55848: [cuirass] workers stalled

Hi Maxime, Maxime Devos writes: > Maxim Cournoyer schreef op zo 19-06-2022 om 22:39 [-0400]: >> There was also an attempt to cross-compile a rust/cargo bootstrap seed >> for other architectures (branch: wip-cross-built-rust) but due to >> complications with building rust as a static archive (it

bug#55848: [cuirass] workers stalled

Maxim Cournoyer schreef op zo 19-06-2022 om 22:39 [-0400]: > There was also an attempt to cross-compile a rust/cargo bootstrap seed > for other architectures (branch: wip-cross-built-rust) but due to > complications with building rust as a static archive (it relies on > dynamic linking for its

bug#55848: [cuirass] workers stalled

On Mon, 20 Jun 2022, at 12:39 PM, Maxim Cournoyer wrote: > That's a known issue with mrustc; it only succeeds with x86_64; the > other architectures have problems. That's a bug the mrustc author would > like to fix, so perhaps in time in will improve (especially if > interested parties can lend a

bug#55848: [cuirass] workers stalled

Hi Mathieu! [...] > A few issues remain for aarch64: > > * grunewald and kreuzberg are not on . > Perhaps they were taken down while the substitute ratio was low to > avoid each worker independently recompiling expensive toolchains? > * rust@1.39.0 (and thus

bug#55848: [cuirass] workers stalled

Mathieu Othacehe writes: Substitutes for aarch64 are a lot healthier now. Thanks Ludovic! * kreuzberg is now successfully building and has been for a while. * ci.guix.gnu.has has 41% of substitutes (a low percentage, but likely a high percentage of toolchains). 0 jobs are queued, presumably

bug#55848: [cuirass] workers stalled

Ricardo Wurmus skribis: > They should be using the local IP instead of routing through the > internet, so /etc/hosts should contain an entry for > > 141.80.167.131 ci.guix.gnu.org Good idea. > “guix deploy” did not work on these nodes due to a serious problem: they > were given *some* x86_64

bug#55848: [cuirass] workers stalled

Ludovic Courtès writes: > Hi, > > (+Cc: guix-sysadmin) > > Tom Fitzhenry skribis: > >>>From following the builds on http://ci.guix.gnu.org/workers , many >> (all?) builds are failing on the following workers: >> >> * grunewald >> * kreuzberg >> * pankow >> >> The builds are failing with the

bug#55848: [cuirass] workers stalled

Hi, (+Cc: guix-sysadmin) Tom Fitzhenry skribis: >>From following the builds on http://ci.guix.gnu.org/workers , many > (all?) builds are failing on the following workers: > > * grunewald > * kreuzberg > * pankow > > The builds are failing with the same error: > > "substitute: updating

bug#55848: [cuirass] workers stalled

Greg Hogan writes: > On Wed, Jun 8, 2022 at 11:32 AM Mathieu Othacehe wrote: >> The aarch64 workers were all idle whereas 70k builds were >> available. Once restarted, they started building again. >From following the builds on http://ci.guix.gnu.org/workers , many (all?) builds are failing on

bug#55848: [cuirass] workers stalled

On Wed, Jun 8, 2022 at 11:32 AM Mathieu Othacehe wrote: > > > Hello, > > The aarch64 workers were all idle whereas 70k builds were > available. Once restarted, they started building again. > > The problem might be that when the server is unavailable for a while the > worker connections expire and

bug#55848: [cuirass] workers stalled

Hello, The aarch64 workers were all idle whereas 70k builds were available. Once restarted, they started building again. The problem might be that when the server is unavailable for a while the worker connections expire and cannot be resumed once the server is available again. Thanks,