It should, we are working with the SC on figuring this out live 
Open for suggestions!
Nix-Community has dropped support for their cuda jobset in response to being blindsided with this announcement.
Unfortunately this setup does not seem to support NixOS 25.05, so I managed to convince zowoq to keep the cuda-stable jobset around until end of year, which matches the nixos-25.05 support cycle.
Now, I wonder what then? Will Flox be providing support for NixOS 25.11 by then?
5 Likes
Martin, thanks for pushing the conversation forward. I think your messages in #nix-community:nixos.org acknowledged the existing solution and zowoq’s work better than anything I could write would. I don’t pretend to answer, but will link some more status updates (which were public anyway, just not highlighted):
- There was a late attempt at some more transparency, on behalf of the CUDA team I guess: build06: init by zowoq · Pull Request #1807 · nix-community/infra · GitHub.
- For the time being, Gaetan volunteered to pick up the GPU Tests effort: there’s some important work happening under GitHub - nix-community/cuda-infra: Machine config for the CUDA team [maintainer=@GaetanLepage], that would be relevant regardless of where it’s hosted.
Personally, I’d still encourage …
- Flox to build master and release branches in addition to unstable, and archive all FODs, despite Flox customers only consuming unstable, because… they’re the only ones legally allowed to do so at the moment, and (by now) it’s literally just a matter of throwing more compute and storage at the problem, less so a matter of workforce.
- “Us” to keep building things outside Flox, because “a private company already does a thing” by no means implies we should stop doing the thing, and because federated multi-party CI is the future of Nixpkgs anyway
10 Likes