#nixos-aarch64 on 2018-10-20

2018-09-23 16:56 gchristensen changed the topic of #nixos-aarch64 to: Get access to the NixOS Community aarch64 build box: https://github.com/nix-community/aarch64-build-box ... todo: https://hydra.nixos.org/jobset/nixpkgs/trunk#tabs-jobs build box status: https://monitoring.nix.ci/d/hkRCcV0mk/instance-metrics?var-instance=aarch64.nixos.community&orgId=1

00:27 tathougies has quit [Quit: Leaving.]

00:27 tathougies has joined #nixos-aarch64

00:28 tathougies has quit [Client Quit]

02:05 lopsided98 has quit [Quit: Disconnected]

02:18 lopsided98 has joined #nixos-aarch64

02:32 orivej has quit [Ping timeout: 244 seconds]

04:43 {`-`}_ has joined #nixos-aarch64

04:44 {`-`} has quit [Remote host closed the connection]

05:31 bzLem0n has joined #nixos-aarch64

05:33 bzLem0n has quit [Client Quit]

07:58 orivej has joined #nixos-aarch64

08:57 Acou_Bass has quit [Ping timeout: 252 seconds]

09:05 Acou_Bass has joined #nixos-aarch64

10:03 FRidh has joined #nixos-aarch64

14:58 Thra11 has joined #nixos-aarch64

15:47 lopsided98 has quit [Ping timeout: 276 seconds]

15:50 lopsided98 has joined #nixos-aarch64

19:09 FRidh has quit [Quit: Konversation terminated!]

21:48 <Thra11> aarch64 rustc 1.29.1 builds fine for me, but the hydra.nix.org build appears to have been killed (OOM?): https://hydra.nixos.org/build/82950500/nixlog/1/tail . a) How can hydra be persuaded that it's a transient failure? b) If it ran out of memory, is it likely to suffer the same problem on a rerun?

22:52 <gchristensen> unlikely to run out of ram ..

22:53 <gchristensen> though not impossible

22:53 <gchristensen> a few times it did get down to bout 6% free

22:54 <gchristensen> (8gb free)

22:54 <samueldr> only 8GB free?

22:55 <gchristensen> yeah, I know -- criminally low

22:55 <gchristensen> anyway, I restarted it