<tom39291> I can see two llvm builds on aarch64 on packet-t2a-3 having hung after building, and eventually timing out: https://hydra.nixos.org/build/89110491 https://hydra.nixos.org/build/90390761
<tom39291> If you compare each build's logs with the previous successful build, you can see it did manage to perform the build. But timed out after 10h.
<tom39291> Anyone know of such hanging issues?
<tom39291> My only aarch64 machine is a rpi, so my ability to reproduce this is limited.
orivej has quit [Ping timeout: 272 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
orivej has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
<sphalerite> tom39291: I'll see if I can reproduce this on the aarch64 community box
<gchristensen> maybe the balance isn't right on resource allocation
<gchristensen> but
<gchristensen> I'd bet if llvm was marked big-parallel, it'd pass okay
<sphalerite> gchristensen: why that?
<sphalerite> gchristensen: it seems odd for it to time out *at the end* of the build because of resource allocation…
<gchristensen> weird
<sphalerite> and aren't all our aarch64 builders big-parallel?
<gchristensen> no
<gchristensen> 1 machine grants each of its 2 jobs 45 cores
<gchristensen> another machine grants each of its 85 jobs 1 core
<sphalerite> aah ok
<gchristensen> plus some other qualcomm and ampere hw
<{^_^}> #57790 (by grahamc, 13 minutes ago, open): Llvm: mark as big parallel
Acou_Bass is now known as eddie
eddie is now known as Guest5970
Guest5970 is now known as Acou_Bass
<sphalerite> wooooo nixos running (somewhat) on my nano pi!
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 245 seconds]
<tom39291> sphaler: Thank you for looking into this. I'll keep my eye on hydra.
<sphalerite> tom39291: couldn't reproduce it :/
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]