!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.120 Servers

Load older messages


SenderMessageTime
24 Mar 2025
@hexa:lossy.networkhexabut apparently https://github.com/NixOS/nixpkgs/pull/367695 has not landed yet14:54:24
@hexa:lossy.networkhexa* but apparently https://github.com/NixOS/nixpkgs/pull/367695 has not landed so far14:54:33
@vcunat:matrix.orgVladimír Čunát That would be ~1 TB / month just from staging* rebuilds for this. 14:59:17
@emilazy:matrix.orgemilyright. I commented as much on the RFC. (from the RFC diff after the conversation earlier it seems like your earlier comment was misinterpreted as "the current normal cache growth rate is 2 TB/month compared to this being 700 GB one time"?)15:00:13
@emilazy:matrix.orgemily(rather than "this would add 2 TB/month rather than 700 GB one time, because of rebuilds")15:00:31
@emilazy:matrix.orgemilyat least, the RFC claims that the current growth rate is 2 TB/month so we shouldn't worry about a one-time increase, but neither of those seems accurate15:00:51
@elvishjerricco:matrix.orgElvishJerriccoSo how much of a problem is this? Can we absorb a 15-30% hit to cache size growth? Or does that make the RFC a non-starter from an infra perspective?15:08:38
@emilazy:matrix.orgemilythe infra team isn't the one paying the bills15:09:03
@toonn:matrix.orgtoonn Wasn't the sponsorship extension based on a commitment to reduce the size of the cache? 15:14:08
@emilazy:matrix.orgemilythat's my understanding, which I also mentioned in https://github.com/NixOS/rfcs/pull/185#issuecomment-274833920015:14:33
@emilazy:matrix.orgemilyI just mean that's more Foundation than it is infra team, AFAIU15:15:05
@emilazy:matrix.orgemilythey're the ones responsible for the bill ultimately15:15:17
@elvishjerricco:matrix.orgElvishJerriccoRedacted or Malformed Event15:23:22
@elvishjerricco:matrix.orgElvishJerriccowrong room :P15:23:32
@raitobezarius:matrix.orgraitobezariusyes, there was even deduplication proposals using CAStore in the past15:28:44
@sinan:sinanmohd.comsinan changed their display name from sinan (we're so back) to sinan.16:00:09
@sinan:sinanmohd.comsinan changed their profile picture.16:00:11
@k900:0upti.meK900Kicked unstable-small to pick up the kernel bumps16:03:25
@hexa:lossy.networkhexaupdated the two oakhost macs to 15.3.218:28:55
25 Mar 2025
@hexa:lossy.networkhexaupdating the remaining macs00:19:41
@hexa:lossy.networkhexaok, all done00:38:54
@k900:0upti.meK900Can someone take a look at what happened to channel-scripts?07:12:58
@k900:0upti.meK900update-nixos-unstable-small.service doesn't seem to be triggering at all07:13:10
@k900:0upti.meK900{894248C5-0566-4A0E-BD57-805DE6447608}.png
Download {894248C5-0566-4A0E-BD57-805DE6447608}.png
07:13:35
@k900:0upti.meK900OK what07:13:37
@vcunat:matrix.orgVladimír Čunát

Mar 25 07:10:25 pluto update-nixos-unstable-small-start[2382223]: channel would go back in time from https://releases.nixos.org/nixos/unstable-small/nixos-25.05beta773513.621f88662af5 to nixos-25.05pre773850.126db443ed3f, >

07:14:29
@vcunat:matrix.orgVladimír ČunátCould that be some side effect of this revert? https://github.com/NixOS/nixpkgs/pull/39290407:15:37
@k900:0upti.meK900Yes07:16:39
@k900:0upti.meK900I think you need to force it now07:16:50
@k900:0upti.meK900 Try running it with FORCE=1 07:17:16

Show newer messages


Back to Room ListRoom Version: 6