| 13 Oct 2021 |
 Piper McCorkle (she/her or they/them) | I guess one way of namespacing would be do spin up an x86_64-linux NixOS VM with binfmt-misc inside, that way those systems don't need to have NixOS building | 05:54:42 |
 Ryan Burns | I wonder if it would be possible to do that and still get KVM accel | 05:56:30 |
| Piper McCorkle (she/her or they/them) | Should be, it's just a regular NixOS VM that happens to have binfmt_misc configured | 05:56:49 |
| Piper McCorkle (she/her or they/them) | Granted the KVM accel won't do much for the binary emulation, but things like Nix would be accelerated | 05:57:11 |
| Piper McCorkle (she/her or they/them) | * Granted the KVM accel won't do much for the binary emulation of the other arch, but things like Nix would be accelerated | 05:57:22 |
| Ryan Burns | True, probably wouldn't make much difference for total build time | 05:57:48 |
| Piper McCorkle (she/her or they/them) | Yep, especially if we spin up a VM and run the whole bootstrap process inside it | 05:58:31 |
| Piper McCorkle (she/her or they/them) | * Yep, especially if we spin up a VM and run the whole bootstrap process inside it, that way there's no boot overhead | 05:58:47 |
 Vladimír Čunát | In reply to @hexa:lossy.network
sent an image. Oh, now I see... at the top of https://hydra.nixos.org/machines That looks like Hydra interpreting something meant as a comment. | 07:46:07 |
 sterni | In reply to @piper:lutris.engineering
What would the hurdles be to add qemu-binfmt to Hydra builders? I'm working on sparc64 and ppc64le bootstrap seeds and investigating the possibility of running the 3-stage build entirely on Hydra, so that they're actually just derived from the x86_64-linux seeds you can build cross packages on hydra as well, I think that would be more worthwhile actually | 08:08:22 |
| sterni | of course you then can't get binary cache for any native packages from hydra | 08:08:38 |
| Piper McCorkle (she/her or they/them) | The first stage of building bootstrap-tools is cross, but the second two stages are native | 08:09:01 |
| sterni | ah right, yeah | 08:09:23 |
| sterni | I wonder how noticeable the performance cost of binfmt_misc would be for us; I think it would hurt us more than e. g. alpine which build riscv64 packages using it since we rebuild everything a lot | 08:10:37 |
 Rick (Mindavi) | There's also a chance of miscompilation due to bugs in the emulator or mismatched feature support, I think. Anyway, afaik it's also very slow | 08:22:22 |
| Piper McCorkle (she/her or they/them) | I am realizing from experience how slow it is... unfortunately I don't know if there's a better option without having a native buildbox, and it would be hard to get a dedicated buildbox for these exotic architectures | 08:23:32 |
| sterni | Does it sound plausible that some Hydra builders are running a Kernel < 5.9? | 10:18:51 |
| Vladimír Čunát | In reply to @sternenseemann:systemli.org
Does it sound plausible that some Hydra builders are running a Kernel < 5.9? t4b does. Generally we probably don't want to rely on that in builds. | 10:20:24 |
| sterni | Vladimír Čunát: bingo :) https://hydra.nixos.org/build/154918256/nixlog/2 | 10:25:20 |
| sterni | but that's easy I'll just disable the test suite if the kernel is too old | 10:25:41 |
| Vladimír Čunát | I suspected it's the only one with old kernel. But I don't think there's just hydra.nixos.org; we also want people to be able to reproduce the build, and 5.9 isn't that old nowadays. | 10:27:59 |
| Vladimír Čunát | * I suspected it's the only one with old kernel. But I don't think there's just hydra.nixos.org; we also want people to be able to reproduce the build, and 5.9 isn't that old nowadays (even though 5.10 has been default on NixOS for some time). | 10:28:41 |
 toonn | Uhm, so I had a job aborted earlier and I started a new evaluation after pushing some more commits but most of the jobs have already "finished" as being aborted. Why is this and can I get them unaborted? | 19:32:04 |
| toonn | *An evaluation aborted rather, I guess. | 19:33:48 |
| sterni | toonn: if they are still the same (hash) they are still aborted | 19:37:48 |
| sterni | I can just restart all aborted ones again | 19:37:54 |
| sterni | * I can just restart all aborted ones again if you link me the evaluation | 19:38:04 |
| toonn | But how would that happen? The commits I pushed touch sphinx. Which caused 1000's of failures before. So I'd expect it to change 1000's of hashes now : s | 19:42:11 |
| Ryan Burns | toonn: you modified the extraPostFetch but didn't change the FOD hash so no hashes changed and nothing will be rebuilt | 19:51:58 |
| toonn | Right... >.< Ok, then I do need the aborted jobs restarted : ) | 19:59:56 |
