| 28 Sep 2025 |
 hexa (signing key rotation when) | it was just what I was used to from the cuda jobsets on nix-community | 17:14:32 |
| hexa (signing key rotation when) | and recursing into pkgsRocm was a non-starter | 17:14:39 |
| hexa (signing key rotation when) | but importing it into the existing jobset is absolutely fine with me | 17:15:21 |
 Lun | Is there a point in still having a separate release-rocm.nix then? I could put the generated list of different-for-rocm packages somewhere in rocm-modules and have release.nix's pull those in under packageJobs without needing a new top level release- file | 18:00:15 |
| Lun | * Is there a point in still having a separate release-rocm.nix then? I could put the generated list of different-for-rocm packages somewhere in rocm-modules and have release.nix pull those in under packageJobs without needing a new top level release- file | 18:00:49 |
 vcunat | Whatever the way, I assume that we want to filter the jobs for x86_64-linux only, so the approach should support that somehow. (Because other platforms are rarely combined with HW where rocm makes sense?) | 18:17:27 |
 K900 | Technically you can have an AMD GPU in an ARM server | 18:20:53 |
| hexa (signing key rotation when) | rocm clang is x86-64-linux only right now | 18:21:08 |
| Lun | yeah I'd like to get the package set working for aarch64 at some point but I don't have the builders for anything but x86_64 and nobody who does has been trying to use it. one laptop with 16gb of RAM does not build a rocmPackages.
jobs will be x86_64-linux only for now | 18:22:44 |
| hexa (signing key rotation when) | https://nix-community.org/community-builders/ | 18:23:28 |
| Lun | How powerful are the aarch64 boxes there? | 18:23:45 |
