!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

386 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

Load older messages


SenderMessageTime
21 May 2025
@domenkozar:matrix.orgDomen Kožarsome installations started to suddenly fail19:24:16
@hexa:lossy.networkhexathey are not infra managed19:35:04
@hexa:lossy.networkhexa ask the folks in #nix-dev:nixos.org 19:35:14
@hexa:lossy.networkhexawell I guess release.nixos.org is kinda infra managed, but we made no changes that I know of19:35:43
@sudoforge:matrix.org@sudoforge:matrix.org joined the room.19:49:49
22 May 2025
@joerg:thalheim.ioMic92I am not aware of any changes.12:18:23
@joerg:thalheim.ioMic92Could it be github doing something with their images?12:18:58
@joerg:thalheim.ioMic92What is the best way to reach garbas these days? 12:20:52
@adam:robins.wtfadamcstephens joined the room.14:02:41
@jfly:matrix.orgJeremy Fleischman (jfly)
In reply to @joerg:thalheim.io
What is the best way to reach garbas these days?
I met him at Planet Nix. He works at Flox, and they have a community Slack: https://go.flox.dev/slack
16:01:05
@domenkozar:matrix.orgDomen Kožarmaybe it was namespace doing an image rollout17:24:01
@lassulus:lassul.uslassulus Mic92 hexa (signing key rotation when) Jeremy Fleischman (jfly) : can one of you take care of https://github.com/NixOS/infra/pull/691 ? we would need that for the nixcon ticket sale to go live 17:39:26
@k900:0upti.meK900Going to start a new unstable-small to get Hydra building the new kernels18:31:31
@k900:0upti.meK900Is Hydra dead20:12:44
@rosscomputerguy:matrix.orgTristan RossSeems like it, I can't connect to it20:13:12
@rosscomputerguy:matrix.orgTristan RossOh, it loaded after like a minute and a half.20:13:58
@adam:robins.wtfadamcstephensIt was being very slow for me earlier20:19:12
@leona:leona.isleonathat very much might have been me. i tried to use the old script to find broken builds, but will now use another approach. in it's current way the script just breaks hydra20:21:20
@hexa:lossy.networkhexaI hope you merged the 5.10 fix20:30:22
@k900:0upti.meK900I did20:30:29
@sudoforge:matrix.org@sudoforge:matrix.orgshhh, the beast is sleeping. don't wake it20:41:26
@leona:leona.isleona Could someone please change stableBranch to true for the 25.05 hydra jobsets? :) 21:30:45
@hexa:lossy.networkhexadone22:04:54
@hexa:lossy.networkhexathat also triggered an eval22:05:20
@leona:leona.isleonathank you! 22:06:55
23 May 2025
@vcunat:matrix.orgVladimír ČunátHuh, I didn't realize that the Hydra's queue runner is dumb enough to attempt building exactly the same derivation twice in parallel. Right now: https://hydra.nixos.org/build/298195286 https://hydra.nixos.org/build/298186259 (note the timestamps etc.) The only luck here is that they got scheduled to the same builder machine and Nix on the machine does deduplicate that.08:08:20
@vcunat:matrix.orgVladimír ČunátThat might be happening a lot now, as 25.05 does not differ much from unstable/master yet - and quite commonly nixpkgs:trunk has significant job overlap nixos:trunk-combined.08:11:23
@vcunat:matrix.orgVladimír Čunát* That might be happening a lot now, as 25.05 does not differ much from unstable/master yet - and quite commonly nixpkgs:trunk has significant job overlap with nixos:trunk-combined.08:11:32
@vcunat:matrix.orgVladimír ČunátHere a darwin case where it scheduled to different machines and really duplicates: https://hydra.nixos.org/build/298195288 https://hydra.nixos.org/build/29820448508:13:41
@vcunat:matrix.orgVladimír Čunát (floorp being a nice test case right now) 08:13:58

Show newer messages


Back to Room ListRoom Version: 6