NixOS CUDA | 283 Members | |
| CUDA packages maintenance and support in nixpkgs | https://github.com/orgs/NixOS/projects/27/ | https://nixos.org/manual/nixpkgs/unstable/#cuda | 58 Servers |
| Sender | Message | Time |
|---|---|---|
| 12 Nov 2025 | ||
| So you get a cache hit, all good then? | 12:39:15 | |
| Yeah, Ari Lotter, might be a good idea to add this cache (as well as Flox's):
| 12:44:00 | |
| Yep, no cache hit with Flox:
| 12:52:31 | |
| (maybe they're having the same build issue, lol) I don't know enough about them tbh | 12:58:09 | |
| Flox are building from their own fork of Nixpkgs. (according to https://flox.dev/blog/the-flox-catalog-now-contains-nvidia-cuda/) Their https://github.com/flox/nixpkgs/tree/unstable is ~10 days old, lol | 13:06:13 | |
| So much for the private sector | 13:06:18 | |
In reply to @daniel-fahey:matrix.orgAre you sure they aren’t just wrapping nix unstable with some hacks for their project? | 15:23:23 | |
| allllllright let's try nixpkgs-review again with the new binary cache :p | 15:30:38 | |
| still building jax, but, uhhhh, we ball | 15:40:02 | |
| Which PR? | 15:56:37 | |
| this one https://github.com/NixOS/nixpkgs/pull/460701 | 15:57:23 | |
yep, workers keep crashing :/] building python3.12-jax-0.8.0 (pytestCheckPhase): replacing crashed worker gw1 | 15:57:38 | |
hm,warning: ignoring the client-specified setting 'sandbox', because it is a restricted setting and you are not a trusted userwarning: ignoring the client-specified setting 'system', because it is a restricted setting and you are not a trusted userwould setting myself as a trusted user fix this, i wonder | 16:02:06 | |
Yeah you might want to use extra-substituters (I never grok'd the difference, if I'm being honest) | 16:06:51 | |
| not sure if it's different with Nix on Ubuntu, but on NixOS, I have to rebuild the system before the binary cache is available. Is there a rebuild step with plain Nix? | 16:08:28 | |
| I reckon they might be in a private repo hinted at in https://github.com/flox/nixpkgs/pull/3#issuecomment-1276439899 But the https://github.com/flox/nixpkgs/tree/unstable is a simple fork that I'd like to see sync'd/rebased from upstream Nixpkgs more frequently. Gaétan Lepage is this is the kind of thing that could be discussed in your CUDA Team meetings, and maybe brought up to the Steering Committee for discussion with Flox? | 16:12:16 | |
Flox is managing their cache internally. As you pointed, they use an internal fork of nixpkgs that is slightly delayed from nixos-unstable (or nixos-unstable-small). It's normal that their cache is less fresh than chache.nixos-cuda.org. | 16:13:41 | |
| The difference is that they have the permission from Nvidia to redistribute their binaries. | 16:14:01 | |
| 😅 | 16:14:45 | |
| i have it in both because i don't understand it <3 | 16:15:52 | |
| also - 100% sure i'm not running out of ram anymore, at only ~400gb/2tb used on the machine, but jax still has crashed workers - and not sure if it's progressing | 16:17:00 | |
| can i pull up interactive logs for its derivation somehow? | 16:17:11 | |
| oh nice, i got a real failure | 16:17:50 | |
Download image.png | 16:18:16 | |
| Another option Ari, is you follow the "Help" button next to the closure link at https://hydra.nixos-cuda.org/build/8123 | 16:18:17 | |
Could just pipe output through tee, but normally at the tail of the the crash, it has the command to run to see the log | 16:19:19 | |
| I'd be interested to see them, see if they're similar to what I saw on nixbuild.net -> you said it crashed during the test stage? | 16:19:53 | |
| *phase | 16:19:56 | |
I also wonder if nixpkgs-review is complicating things | 16:20:33 | |
| grabbing logs! | 16:22:05 | |