!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

485 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.152 Servers

Load older messages


SenderMessageTime
26 Jun 2026
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)
In reply to @dramforever:matrix.org
beware of appendPatch problems on darwin with unsandboxed builds https://github.com/NixOS/nix/issues/14751
Those were fixed with build dir changes
08:23:06
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)drv name is no longer in the build dir name08:23:23
@grimmauld:m.grimmauld.deGrimmauld (any/all) more openmp things? Is there a list of things it is currently attempting to build eating all the cpu? 08:23:54
@vcunat:matrix.orgVladimír ČunátIt's honestly tiring to chase individual packages not respecting such constraints, as we have way too many in nixpkgs.08:25:06
@jappie:jappie.devjappieyou can view a list of jobs running on each machine here: https://hydra.nixos.org/machines08:25:08
@shadowrz:nixos.devYorusaka Miyabisleepy-brown: idle08:25:46
@shadowrz:nixos.devYorusaka Miyabi🤔08:25:48
@vcunat:matrix.orgVladimír ČunátBut right now it's all python stuff again, apparently.08:25:54
@grimmauld:m.grimmauld.deGrimmauld (any/all) A global OMP_NUM_THREADS = 1 default may make sense after all... 08:25:58
@grimmauld:m.grimmauld.deGrimmauld (any/all) Anything pulling numpy/scipy is potentially doing OMP 08:26:10
@vcunat:matrix.orgVladimír ČunátThat one is reserved for big-parallel build.s08:26:17
@vcunat:matrix.orgVladimír Čunát* That one is reserved for big-parallel builds.08:26:25
@vcunat:matrix.orgVladimír Čunát* But right now it's all python processes again, apparently.08:27:41
@hexa:lossy.networkhexa

Evaluation running since: 5h ago

08:50:04
@hexa:lossy.networkhexahrm hrm08:50:07
@vcunat:matrix.orgVladimír ČunátNo, it's not really running.08:50:52
@hexa:lossy.networkhexa
hydra    1061238  3.5  1.9 5161216 5115028 ?     S    03:20  11:33 /nix/store/6plwsm6pkq79yjv4xvy8csk2pd4hzr67-perl-5.42.0/bin/perl /nix/store/sbz0i4y97gslxvb2yx7qyvwfy743wvkl-hydra-0.1.20260625.39515ec/bin/.hydra-eval-jobset-wrapped nixpkgs unstable
08:51:04
@vcunat:matrix.orgVladimír Čunáthttps://github.com/NixOS/hydra/issues/181208:51:13
@vcunat:matrix.orgVladimír ČunátIt might be just an UI issue.08:51:20
@hexa:lossy.networkhexabut the process is actually running?08:51:44
@hexa:lossy.networkhexa
# strace -fp 1061238
strace: Process 1061238 attached
restart_syscall(<... resuming interrupted restart_syscall ...>
08:51:58
@vcunat:matrix.orgVladimír ČunátIt started about 5h ago and produced an eval.08:53:08
@hexa:lossy.networkhexaso it does not exit properly anymore and blocks new evals?08:53:34
@hexa:lossy.networkhexakilled the job08:53:58
@hexa:lossy.networkhexait will certainly return08:54:08
@vcunat:matrix.orgVladimír ČunátUh, log for that service only has the last 2 hours.08:54:11
@hexa:lossy.networkhexayeah, queue-runner spam08:54:19
@hexa:lossy.networkhexaand journal being limited at 4.0G right now08:54:37
@vcunat:matrix.orgVladimír ČunátI'm quite sure that Hydra was showing the "running" status even after finishing and eval and then finished some other evals, too.08:55:44
@vcunat:matrix.orgVladimír Čunát(and it still showed the running status on the first one)08:55:56

Show newer messages


Back to Room ListRoom Version: 6