!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

382 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.117 Servers

Load older messages


SenderMessageTime
17 Apr 2025
@joerg:thalheim.ioMic92Or do reviews go faster these days?12:18:46
@joerg:thalheim.ioMic92Not suggesting to stop open pull requests but this way we can have an integration branch for ourself.12:22:19
@hexa:lossy.networkhexaInfra call in 90 minutes14:30:33
@hexa:lossy.networkhexa
In reply to @joerg:thalheim.io
hexa (signing key rotation when): do we maybe want to fork the nixos-mailserver into nixos infra for our patches?
Yeah, sure.
14:31:16
@vcunat:matrix.orgVladimír Čunát(bad timing for me, as most weeks)14:39:11
@hexa:lossy.networkhexahttps://jitsi.lassul.us/nixos-infra15:59:46
@jfly:matrix.orgJeremy Fleischman (jfly)
In reply to @hexa:lossy.network
Yeah, sure.
I would appreciate this for both us and my personal mailserver.
16:00:39
@jfly:matrix.orgJeremy Fleischman (jfly)If y'all are discussing this at today's meeting, feel free to assign the work to me 16:01:03
@hexa:lossy.networkhexa Mic92: you coming? 16:02:45
@joerg:thalheim.ioMic92Ah meeting 16:03:26
@joerg:thalheim.ioMic92Maybe in some minutes. Still in the U-Bahn 16:03:30
@hexa:lossy.networkhexa Mic92: can you run treefmt in a dedicated ci job, so it doesn't pollute every other build job? 20:41:05
@hexa:lossy.networkhexa * Mic92: can you migrate treefmt into a dedicated ci job, so it doesn't pollute every other build job? 20:41:14
18 Apr 2025
@joerg:thalheim.ioMic92 @hexa:lossy.network: what does polluting mean? 05:05:54
@joerg:thalheim.ioMic92It runs currently once per architecture.05:06:12
@hexa:lossy.networkhexaRedacted or Malformed Event08:18:14
@hexa:lossy.networkhexaah, so maybe it is just named confusingly08:18:18
@hexa:lossy.networkhexanix-build ($arch)08:18:26
@joerg:thalheim.ioMic92We build all packages in one pipeline to avoid spawning too many different vms and than all machine configurations in one job each to not run into disk space issues.08:36:26
@joerg:thalheim.ioMic92* We build all packages in one job to avoid spawning too many different vms and than all machine configurations in one job each to not run into disk space issues.08:36:41
@joerg:thalheim.ioMic92and it's only re-building packages that are not cached. Treefmt will run in most cases because each source change will trigger a rebuild08:37:12
@joerg:thalheim.ioMic92we can re-name it to checks to make it less confusing.08:38:52
@hexa:lossy.networkhexaYeah, that could help already 🙂 08:39:55
@hexa:lossy.networkhexaThanks!09:00:12
@bot-wxt1221:matrix.orgBot_wxt1221 joined the room.12:08:39
@mschwaig:matrix.orgMartin Schwaighofer joined the room.15:13:42
@enzime:nixos.dev@enzime:nixos.dev left the room.21:23:52
20 Apr 2025
@vcunat:matrix.orgVladimír Čunát

Any idea what's this?
https://hydra.nixos.org/jobset/nixpkgs/staging#tabs-errors

process ended prematurely at [...]/bin/.hydra-eval-jobset-wrapped line 405.

18:21:46
@vcunat:matrix.orgVladimír Čunát *

Any idea what this is?
https://hydra.nixos.org/jobset/nixpkgs/staging#tabs-errors

process ended prematurely at [...]/bin/.hydra-eval-jobset-wrapped line 405.

18:22:10
@vcunat:matrix.orgVladimír Čunát *

Any idea what this is about?
https://hydra.nixos.org/jobset/nixpkgs/staging#tabs-errors

process ended prematurely at [...]/bin/.hydra-eval-jobset-wrapped line 405.

18:22:22

Show newer messages


Back to Room ListRoom Version: 6