| 28 Oct 2024 |
 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 |
| adamcstephens | Is it Apple Silicon? Would you be willing to give over administrative control? (not sure if this is a requirement or not) | 18:50:04 |
| 2 Nov 2024 |
 aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | Ofborg eval seems to be blocked again? (How do we check queue status?) | 15:56:05 |
 hexa | url in th e topic | 16:01:55 |
| hexa | * url in the topic | 16:01:58 |
| aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | In reply to @hexa:lossy.network
url in th e topic The evaluation queue, not build queue | 16:45:58 |
| hexa | the upper graph | 16:46:14 |
| hexa |
ofborg_queue_evaluator_waiting
| 16:46:21 |
| aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | Oh I see | 16:50:58 |
| adamcstephens | 
Download image.png | 17:57:53 |
| adamcstephens | this doesn't seem sustainable | 17:58:01 |
 Artturin | We need nuclear ofborg | 17:58:23 |
| adamcstephens | the many hours wait just to get the ofborg eval is starting to become annoying | 21:30:05 |
| Tristan Ross | I've just been running nixpkgs-review on my system but yeah, waiting for Ofborg isn't great. | 21:36:31 |
