!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

384 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
1 Mar 2025
@hexa:lossy.networkhexathanks for taking care of that ecosystem 🙂 01:29:56
@hexa:lossy.networkhexapaused unstable-small due to https://github.com/NixOS/nixpkgs/pull/38587903:52:38
@hexa:lossy.networkhexa* cancelled unstable-small due to https://github.com/NixOS/nixpkgs/pull/38587903:52:52
@hexa:lossy.networkhexaok, revert has been merged, evaling unstable-smol05:02:43
@hexa:lossy.networkhexatrying on a 40C machine and I'm at 8% after 2h40m 😄 05:16:25
@hexa:lossy.networkhexawe05:16:32
@hexa:lossy.networkhexa* we'll have to see how this plays out on hydra05:16:39
@hexa:lossy.networkhexawe have epyc 9454p (48C/96T) and schedule 4 big-parallel jobs with 24 "cores"05:18:04
@hexa:lossy.networkhexa* we have epyc 9454p (48C/96T) and schedule up to 4 big-parallel jobs with 24 "cores"05:18:15
@hexa:lossy.networkhexa
  nix.settings = {
    cores = 24;
    max-jobs = 4;
    system-features = [ "big-parallel" ];
  };
05:18:29
@hexa:lossy.networkhexaRedacted or Malformed Event05:19:41
@hexa:lossy.networkhexa

[40 jobs | 9% 389/4212 @ 0.0/s | 2:46:42 | ETA 27:18:26 ]

05:26:06
@hexa:lossy.networkhexaI mean, these are Skylake Cores, so I'm not sure what that means 😄 05:28:22
@hexa:lossy.networkhexahttps://www.intel.com/content/www/us/en/products/sku/123550/intel-xeon-silver-4114-processor-13-75m-cache-2-20-ghz/specifications.html05:28:41
@hexa:lossy.networkhexaI sure hope that package won't surprise me in python-updates one day05:29:14
@vcunat:matrix.orgVladimír Čunát If it's 4h with 128 threads, I don't think it will fit into the 10h default limit in our current infra config. (--cores 24 for big-parallel mentioned here; I didn't verify now) 06:57:47
@vcunat:matrix.orgVladimír ČunátBut that's easy to override per job.06:58:34
@hexa:lossy.networkhexawhere is the default limit set?06:59:30
@hexa:lossy.networkhexaa meta default?06:59:49
@hexa:lossy.networkhexaI think we only configure a max-silent-time on the builders07:00:17
@hexa:lossy.networkhexaand a max-unsupported-time on the queue-runner07:00:23
@hexa:lossy.networkhexaRedacted or Malformed Event07:00:28
@vcunat:matrix.orgVladimír Čunát .meta.timeout 07:01:05
@hexa:lossy.networkhexa
pkgs/applications/networking/browsers/chromium/browser.nix
121:    timeout = 172800; # 48 hours (increased from the Hydra default of 10h)
07:01:34
@hexa:lossy.networkhexa🤡07:01:36
@hexa:lossy.networkhexa *
pkgs/applications/networking/browsers/chromium/browser.nix
121:    timeout = 172800; # 48 hours (increased from the Hydra default of 10h)
pkgs/development/tools/electron/common.nix
287:    timeout = 172800; # 48 hours (increased from the Hydra default of 10h)
07:01:49
@hexa:lossy.networkhexameta.timeout is not set by default, so … where is the default? 😄 07:02:35
@vcunat:matrix.orgVladimír ČunátI think it's in Hydra config.07:02:50
@hexa:lossy.networkhexaimage.png
Download image.png
07:03:04
@hexa:lossy.networkhexa
, timeout => getMeta($buildInfo->{meta}->{timeout}, 36000)
07:03:33

Show newer messages


Back to Room ListRoom Version: 6