!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

387 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
25 May 2025
@uep:matrix.orguepthanks, that will be easier than restarting mjolnir when users fall in the pit00:28:07
@dramforever:matrix.orgdramforeverWhat is going on with the iso and ova images in https://channels.nixos.org/?prefix=nixos-unstable/16:50:30
@dramforever:matrix.orgdramforeverwhy are there seemingly extremely outdated images here16:51:08
@hexa:lossy.networkhexaprobably symlinks we stopped updating a while ago16:54:04
@hexa:lossy.networkhexa iirc emily looked into that 16:54:10
@k900:0upti.meK900Yes those are old symlinks16:54:32
@k900:0upti.meK900The -graphical images should be the up to date ones16:54:37
@hexa:lossy.networkhexa ignore the ones with the ?prefiix= set 16:54:43
@hexa:lossy.networkhexa * ignore the ones with the ?prefix= set 16:54:51
@me:indeednotjames.comemilyhttps://channels.nixos.org/?prefix=nixos-unstable/ vs https://channels.nixos.org/nixos-unstable16:56:34
@dramforever:matrix.orgdramforeveri just realized the "symlinks" are 404 anyway17:09:45
@dramforever:matrix.orgdramforeveranyway thanks for the tips17:09:53
26 May 2025
@entheogenesis:matrix.org@entheogenesis:matrix.org left the room.03:59:12
@federicodschonborn:matrix.org@federicodschonborn:matrix.org changed their display name from This LEGO® Worm™ is licensed under the terms of the he/him or they/them pronouns, at your choice to LEGO® Worm™ (Asbestos Flavored!).13:15:48
27 May 2025
@federicodschonborn:matrix.org@federicodschonborn:matrix.org changed their display name from LEGO® Worm™ (Asbestos Flavored!) to LEGO® Worm™ (Now Only 1 krad!).14:46:06
28 May 2025
@uep:matrix.orgueptrunk-combined builds seem to be inordinately slow lately. I realise we're in that period where there's an extra release branch in the workload, but even so.. it seems worse than it has been in other cycles. Is it just my perception, or something else contributing as well?03:18:44
@hexa:lossy.networkhexawe're coming out of a staging-24.11 cycle, not sure10:03:52
@hexa:lossy.networkhexa we use grafana to observe the pace of hydra usually 10:04:21
@hexa:lossy.networkhexaand what you can see is that is has no linux runnables10:04:51
@vcunat:matrix.orgVladimír ČunátThe "builds ingestion" is almost always what blocks us (if speaking about linux).10:05:56
@vcunat:matrix.orgVladimír ČunátThat's a long-term property.10:06:28
@vcunat:matrix.orgVladimír Čunát"Steps completed per minute" isn't much lower than usually, I'd say.10:07:16
@uep:matrix.orguepi'm going by https://hydra.nixos.org/jobset/nixos/trunk-combined, and the fact that for the last.. quite a few days, it seems the build from the previous day hasn't finished by the time the next one starts. And even with relatively low numbers of jobs to run (8k, vs 120k) it's taking more than a day to finish. I realise this isn't the total picture, i'm not looking at overall throughput or jobs10:11:42
@hexa:lossy.networkhexathis relates to the "build ingestion" in that we don't currently get enough runnables to saturate our linux builders10:14:30
@hexa:lossy.networkhexausually restarting the queue-runner can tip the balance again10:15:03
@vcunat:matrix.orgVladimír ČunátRedacted or Malformed Event10:15:16
@uep:matrix.orguepoh, build ingestion is on-boarding of jobs to run, not ingestion of build results... makes more sense now10:24:33
@hexa:lossy.networkhexahttps://github.com/NixOS/hydra/commit/720db63d52ebcbda617603e7aa5b5c750cc6afec was the last change to the scheduling logic10:29:52
@hexa:lossy.networkhexawe've run with that since around april 29th I would say10:31:51
@hexa:lossy.networkhexabut that's in the dispatcher, not the ingestor10:32:15

Show newer messages


Back to Room ListRoom Version: 6