!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

382 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.118 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
28 Sep 2025
@vcunat:matrix.orgVladimír ČunátI suspect we did have a tool for evaluating just a particular subset of attributes, but I'm not sure about efficiency.15:08:22
@vcunat:matrix.orgVladimír ČunátEssentially, I meant to take whatever you propose for a separate jobset and plug it in. The cost shouldn't differ significantly.15:09:16
@7c6f434c:nitro.chat7c6f434cAsk ROCm-interested people to maintain release-rocm.nix with things they care about (which can be sometimes linted locally, but no need to check completeness on every eval), then import it in the main release?15:12:56
@lt1379:matrix.orgLunIf I import release-rocm's jobs into release do I need to make sure all the names end up unique or it'll break? So if release-rocm.nix is making an "openmpi" job that needs to be something else to be valid to add in release.nix and not conflict with the default openmpi15:29:48
@lt1379:matrix.orgLunhttps://github.com/LunNova/nixpkgs/blob/push-kuknstozqsvo/pkgs/top-level/release-rocm.nix is what I have as an attempt at a release-rocm.nix but I'm not clear on what importing it in the main release properly would look like15:42:20

Show newer messages


Back to Room ListRoom Version: 6