!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

388 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.121 Servers

Load older messages


SenderMessageTime
21 Aug 2025
@joerg:thalheim.ioMic92Will join in 5 min16:06:57
@jfly:matrix.orgJeremy Fleischman (jfly)nevermind, looks like i have access16:07:54
@jfly:matrix.orgJeremy Fleischman (jfly)err, view only access. so edit would be nice16:10:16
@jfly:matrix.orgJeremy Fleischman (jfly)oh, silvan's here. we'll get access =)16:10:50
22 Aug 2025
@elikoga:matrix.orgelikoga changed their profile picture.17:28:52
@winter:catgirl.cloudWinter you 21:58:04
@winter:catgirl.cloudWinter* you'd think the drv would always be available on mimas?21:58:16
@winter:catgirl.cloudWinterunless we just like... gc drvs ~consistently21:58:26
@winter:catgirl.cloudWinterwhich would explain it21:58:31
@winter:catgirl.cloudWinterbut either way surprised this isn't persisted in the hydra db21:58:40
@hexa:lossy.networkhexawe keep derivations, but not outputs22:06:08
23 Aug 2025
@dgrig:erethon.comdgrig

Copy pasting from the nix manpage:

keep-derivations ⟨#conf-keep-derivations⟩

          If  true  (default), the garbage collector will keep the derivations from which non-garbage store paths were built. If false,
          they will be deleted unless explicitly registered as a root (or reachable from other roots).

          Keeping derivation around is useful for querying and traceability (e.g., it allows you to ask with what dependencies  or  op‐
          tions  a  store  path was built), so by default this option is on. Turn it off to save a bit of disk space (or a lot if keep-
          outputs is also turned on).

Since we're gc'ing outputs and it specifies "will keep the derivations from which non-garbage store paths were built", I believe this will also gc derivations?

00:34:24
@hexa:lossy.networkhexaah, yeah00:35:17
25 Aug 2025
@federicodschonborn:matrix.org@federicodschonborn:matrix.org changed their display name from Cat McFishface 🏳️‍🌈 (he/they) to Mr. Bones (he/they).13:37:34
26 Aug 2025
@winter:catgirl.cloudWinteris it expected that channels.nixos.org lags behind the hydra jobsets? e.g. https://hydra.nixos.org/jobset/nixos/trunk-combined#tabs-evaluations, i fetched nixos-unstable on 2025-08-25 10:55 -0400 and got https://hydra.nixos.org/eval/1817796 from the 19th21:58:21
@winter:catgirl.cloudWinter~5-6 days of lag seems... odd?21:58:35
@rvdp:infosec.exchangeRamses 🇵🇸Those evals didn't cause channel bumps, IIUC. The tested job was broken for them22:35:48
@rvdp:infosec.exchangeRamses 🇵🇸So that's intended22:36:21
@rvdp:infosec.exchangeRamses 🇵🇸 Winter: ^ 22:36:37
27 Aug 2025
@vcunat:matrix.orgVladimír ČunátDetails are in https://wiki.nixos.org/wiki/Channel_branches#Internal_channel_update_process05:04:03
@arianvp:matrix.orgArianAggregate jobs always trip me up. Especially because they're so hard to find in the hydra UI. Wish we pinned them to the top of the eval view or something 08:31:30
@vcunat:matrix.orgVladimír ČunátYou'd better use https://status.nixos.org/08:33:53
@vcunat:matrix.orgVladimír ČunátHydra itself does not know that some jobs are special.08:34:18
@vcunat:matrix.orgVladimír Čunát(in the sense that they block channels)08:34:33
@vcunat:matrix.orgVladimír ČunátThat logic is external: https://github.com/NixOS/nixos-channel-scripts/blob/master/mirror-nixos-branch.pl08:35:14
@hexa:lossy.networkhexawill reboot haumea and mimas for an update and the nftables migration13:35:22
@hexa:lossy.networkhexanow that we've essentially run out of linux runnables 😉13:35:42
@hexa:lossy.networkhexaearlier we had 140 copying jobs and the load was >12013:41:25
28 Aug 2025
@drupol:matrix.org@drupol:matrix.org left the room.08:14:27
@sbc64:matrix.orgsbc64 changed their profile picture.14:23:32

Show newer messages


Back to Room ListRoom Version: 6