| 22 Oct 2024 |
 iv-nn | but the PR has been reviewed, it's just the CI that's been stuck on wait. I know aarch64-darwin is over capacity but the run has been waiting for 1 month and 20 days. Is it normal to be this much? | 23:23:53 |
 adamcstephens | It’s surely not still waiting. | 23:24:14 |
| adamcstephens | Do the rebase and hopefully it’ll run in the next couple days | 23:24:38 |
| adamcstephens | It wasn’t clear from your initial message you were talking about a specific build :) | 23:25:11 |
| adamcstephens | People also wait two months on reviews | 23:25:40 |
| iv-nn | Yeah, sorry. I already asked here and got no response, so I went lazy and did not provide the full context again. | 23:25:55 |
| 27 Oct 2024 |
 K900 | Anyone know why an eval didn't get kicked off in https://github.com/NixOS/nixpkgs/pull/351498/commits | 09:07:06 |
| K900 | * Anyone know why an eval didn't get kicked off in https://github.com/NixOS/nixpkgs/pull/351498 | 09:07:08 |
 Lily Foster | In reply to @k900:0upti.me
Anyone know why an eval didn't get kicked off in https://github.com/NixOS/nixpkgs/pull/351498/commits (github ate webhook maybe? it's happened sometimes. but someone would probably want to check logs to be sure) | 14:42:39 |
| 28 Oct 2024 |
 loudgolem | do aarch64-linux builders have only 129MB ram? virtualisation.memorySize = 256; doesn't work (it does in x86_64-linux) | 15:22:58 |
| loudgolem | * do aarch64-linux builders have only 129MB ram?
virtualisation.memorySize = 256; doesn't work (it does in x86_64-linux) | 15:23:12 |
| loudgolem | I can't seem to add additional swap either without getting swapper/0 invoked oom-killer in a nixos test | 15:25:36 |
| loudgolem | * I can't seem to add additional swap either, getting swapper/0 invoked oom-killer in a nixos test | 15:26:12 |
| loudgolem | * do aarch64-linux builders have only 129MB ram? (what free -h reports)
virtualisation.memorySize = 256; doesn't work (it does in x86_64-linux) | 15:27:23 |
| Lily Foster | In reply to @phanirithvij:matrix.org
do aarch64-linux builders have only 129MB ram? virtualisation.memorySize = 256; doesn't work (it does in x86_64-linux) can you link the PR you're having trouble with? | 16:24:07 |
 Tristan Ross | In reply to @phanirithvij:matrix.org
do aarch64-linux builders have only 129MB ram? (what free -h reports)
virtualisation.memorySize = 256; doesn't work (it does in x86_64-linux) Afaik they have over 64GB | 16:49:30 |
| Tristan Ross | The problem is multiple things using memory, maybe it'll work with a rerun | 16:50:35 |
| loudgolem | But are flaky nixos tests fine? | 16:51:07 |
| loudgolem | I have a pr for swapspace (a dynamic swap space manager which grows/shrinks disk into swap)
And to test it I have to starve the vm to be almost out of memory, but it is occasionally failing the test | 16:53:00 |
| loudgolem | * I have a pr for swapspace (a dynamic swap space manager which grows/shrinks disk into swap)
And to test it I have to starve the vm to be almost out of memory (when swapspace beings to work), but it is occasionally failing the test | 16:53:19 |
| loudgolem | * I have a pr for swapspace (a dynamic swap space manager which grows/shrinks disk into swap)
And to test it I have to starve the vm to be almost out of memory (when swapspace beings to work), but it is occasionally failing the test and getting oomd | 16:53:30 |
| loudgolem | * But are flaky nixos tests allowed? | 16:54:24 |
| loudgolem | https://github.com/NixOS/nixpkgs/pull/348588 | 16:54:49 |
| Tristan Ross | In reply to @phanirithvij:matrix.org
But are flaky nixos tests allowed? It depends on what way you mean by flaky. If it fails because the builder OOM's, that's not flaky. That's just the builder being unreliable. | 16:55:59 |
| loudgolem | got it. I guess I was mistaken about the 129mb limit, thanks | 16:57:34 |
| loudgolem | * got it. I guess I was also mistaken about the 129mb limit, thanks | 16:57:40 |
 @philip4g:matrix.org | Is there any opportunity for me to contribute my Mac hardware (Intel or ARM) for NixOS automated builds? | 22:39:06 |
| adamcstephens | In what capacity? | 22:54:09 |
| 29 Oct 2024 |
 @rick:matrix.ciphernetics.nl | Possibly for ofborg and no for hydra, I think | 21:45:22 |
| 30 Oct 2024 |
| @philip4g:matrix.org | In reply to @adam:robins.wtf
In what capacity? I heard that there is a shortage of Mac hardware in OfBorg, causing auto builds to take a very long time. I have some hardware that OfBorg could use remotely, if such a decentralized solution is feasible. | 18:38:47 |
