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

Load older messages


SenderMessageTime
1 Dec 2025
@hexa:lossy.networkhexaI expect we would need to update channels.nix at least18:14:19
@hexa:lossy.networkhexabut beyond that?18:14:25
@vcunat:matrix.orgVladimír Čunát If we call this one nixpkgs/unstable, I guess we should rename nixos/release-25.11 to nixos/25.11? 18:48:36
@vcunat:matrix.orgVladimír Čunát(i.e. naming after the corresponding channel)18:49:01
@vcunat:matrix.orgVladimír Čunát * If we call this one nixpkgs/unstable, I guess we should e.g. rename nixos/release-25.11 to nixos/25.11? 18:49:25
@k900:0upti.meK900I think we should do that for all the channels yes18:50:58
@emilazy:matrix.orgemily (can we get nixpkgs-25.11 that is the same as nixpkgs-unstable instead of nixpkgs-25.11-darwin that omits Linux packages for some reason?) 18:51:55
@emilazy:matrix.orgemily(I guess it's too late for that for 25.11 now)18:51:59
@vcunat:matrix.orgVladimír ČunátThat's technically possible, but I'm not too fond of the duplicated jobs.18:52:58
@vcunat:matrix.orgVladimír Čunát(it would be over quarter of million of them)18:54:03
@hexa:lossy.networkhexalet's try one first 😄 18:54:18
@hexa:lossy.networkhexaeval was successful at least18:54:35
@vcunat:matrix.orgVladimír ČunátYes, sure, I wouldn't rename stable jobsets before some grace period. 18:55:39
@emilazy:matrix.orgemily(it seems very dumb that Hydra can't just handle duplicate jobs efficiently…)18:57:58
@emilazy:matrix.orgemily(but I guess I'm not volunteering to dive into that code to fix it either, so)18:58:16
@vcunat:matrix.orgVladimír ČunátIt will even attempt to build the same .drv twice in parallel.19:00:57
@hexa:lossy.networkhexainfra is currently based on https://github.com/NixOS/infra/pull/90619:32:54
@hexa:lossy.networkhexaI'll try to adapt the builders changes, there has been a conflict since I made that other pr19:33:16
@hexa:lossy.networkhexa
diff --git a/channels.nix b/channels.nix
index 8aeaa13..0de0878 100644
--- a/channels.nix
+++ b/channels.nix
@@ -35,7 +35,7 @@ rec {
       status = "rolling";
     };
     "nixpkgs-unstable" = {
-      job = "nixpkgs/trunk/unstable";
+      job = "nixpkgs/unstable/unstable";
       status = "rolling";
     };
 
20:01:29
@hexa:lossy.networkhexadeployed to pluto20:01:35
@hexa:lossy.networkhexanext we rename unstable to tested? 😛 20:01:44
@hexa:lossy.networkhexa* next we rename the unstable job to tested? 😛 20:01:52
@k900:0upti.meK900Yes please20:12:21
@vcunat:matrix.orgVladimír Čunát And the darwin-tested job? 20:16:23
@vcunat:matrix.orgVladimír Čunát * And the darwin-tested job? 😅 20:16:39
2 Dec 2025
@hexa:lossy.networkhexa c1cb7d097cb2..8c29968b3a94 nixpkgs-unstable -> origin/nixpkgs-unstable 00:41:12
@hexa:lossy.networkhexa *
   c1cb7d097cb2..8c29968b3a94  nixpkgs-unstable                 -> origin/nixpkgs-unstable
00:41:17
@hexa:lossy.networkhexadoing the same for trunk-combined00:41:36
@vcunat:matrix.orgVladimír Čunát

Uh, weird

Aborted: error: AWS error uploading '28gak3chr8k7ip9f5mhaxw4zj325ar5q.ls': Unable to parse ExceptionName: BadDigest Message: The CRC64NVME you specified did not match the calculated checksum. (request id: SE0B3BVH75C582A4)

07:59:52
@vcunat:matrix.orgVladimír ČunátJust noticed that on https://hydra.nixos.org/build/315369795#tabs-buildsteps08:00:19

Show newer messages


Back to Room ListRoom Version: 6