!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

410 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.125 Servers

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


SenderMessageTime
28 Sep 2025
@vcunat:matrix.orgVladimír Čunát *

OK, I assumed this pkgsRocm would be just that diff mentioned in

that list is too expensive to generate on every eval, but that is also not really required, it can gradually be adapted to what is needed

Because we don't want huge amount of duplicate jobs on Hydra (even if the hashes are the same in them).

15:05:41
@vcunat:matrix.orgVladimír Čunát🤔 anyway, that was just a quick thought. Maybe someone will have a better suggestion.15:06:51
@hexa:lossy.networkhexarecursing into pkgsRocm would duplicate eval time15:07:42
@hexa:lossy.networkhexa* recursing into pkgsRocm would double eval time15:08:04
@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

Show newer messages


Back to Room ListRoom Version: 6