!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

389 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
14 Feb 2025
@Ericson2314:matrix.orgJohn EricsonCI passed, the workaround for nix-eval-jobs worked!02:17:19
@joerg:thalheim.ioMic92Merged02:37:06
@Ericson2314:matrix.orgJohn Ericson https://github.com/nix-community/nix-eval-jobs/pull/353 Mic92 if you would be interested in having some sort of nix-next branch like I do for hydra, that would be nice 03:37:39
@Ericson2314:matrix.orgJohn Ericsonnbd if not (and going back and forth between upstream nix and nixpkgs nix is annoying)03:37:56
@Ericson2314:matrix.orgJohn Ericson otherwise a nix-next branch in hydra would have to point to a forked repo, which makes for a gross history 03:38:30
@Ericson2314:matrix.orgJohn Ericson(I like to do things on Hydra and Nix master together, and then merge the branch in Hydra once Nix is released)03:38:49
@sinan:sinanmohd.comsinan changed their profile picture.12:15:49
15 Feb 2025
@benjb83:matrix.orgBenjB83 joined the room.10:19:21
@benjb83:matrix.orgBenjB83 changed their display name from Benjamín Buske to BenjB83.10:43:12
16 Feb 2025
@clhodapp:matrix.orgChris Hodapp joined the room.07:06:40
@vcunat:matrix.orgVladimír Čunát

The queue runner seems quite unstable now:

[root@mimas:~]# journalctl -u hydra-queue-runner.service -r | grep -F 'Main process exited'
Feb 16 09:16:02 mimas systemd[1]: hydra-queue-runner.service: Main process exited, code=dumped, status=11/SEGV
Feb 16 08:32:08 mimas systemd[1]: hydra-queue-runner.service: Main process exited, code=dumped, status=11/SEGV
Feb 16 06:26:30 mimas systemd[1]: hydra-queue-runner.service: Main process exited, code=dumped, status=11/SEGV
Feb 16 05:15:12 mimas systemd[1]: hydra-queue-runner.service: Main process exited, code=dumped, status=11/SEGV
Feb 16 04:44:47 mimas systemd[1]: hydra-queue-runner.service: Main process exited, code=dumped, status=11/SEGV
Feb 16 01:58:56 mimas systemd[1]: hydra-queue-runner.service: Main process exited, code=dumped, status=11/SEGV
Feb 15 17:48:36 mimas systemd[1]: hydra-queue-runner.service: Main process exited, code=dumped, status=11/SEGV
09:57:15
@vcunat:matrix.orgVladimír Čunát

The two traces with dump end with exactly the same gdb line and further down there are minimal differences.

(gdb) bt
#0  0x0000000000425fe6 in State::builder(std::shared_ptr<State::MachineReservation>) [clone .cold] ()
#1  0x0000000000493ac5 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (State::*)(std::shared_ptr<State::MachineReservation>), State*, std::shared_ptr<State::MachineReservation> > > >::_M_run() ()
#2  0x00007f2b802be6d3 in execute_native_thread_routine () from /nix/store/4gk773fqcsv4fh2rfkhs9bgfih86fdq8-gcc-13.3.0-lib/lib/libstdc++.so.6
#3  0x00007f2b7ff5fd02 in start_thread (arg=<optimized out>) at pthread_create.c:447
#4  0x00007f2b7ffdf3ac in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
10:05:49
@vcunat:matrix.orgVladimír ČunátIf I read it right, it's trying to dereference a NULL pointer with a 24B offset.10:17:23
@hexa:lossy.networkhexaI think we've seen this particular trace for most of the last year 🫣11:55:05
@hexa:lossy.networkhexawondering if its related to this change https://github.com/NixOS/hydra/commit/36e25d8fd2fe48132cffdf07ca0a564907758b2111:57:05
@vcunat:matrix.orgVladimír ČunátWith this rate of crashes we'll be unable to finish builds like chromium.12:08:39
@vcunat:matrix.orgVladimír Čunát(it never stays up for a few hours straight)12:09:03
@hexa:lossy.networkhexaok, will revert to test in a bit12:25:05
@hexa:lossy.networkhexaor rather apply this https://git.lix.systems/the-distro/hydra/commit/fb9e29d4d0f2f591cd1d706fd3b7334af7d34b8412:26:57
@hexa:lossy.networkhexaapplied12:29:35
@hexa:lossy.networkhexa* deployed12:29:51
@k900:0upti.meK900Running a new eval on next12:32:07
@vcunat:matrix.orgVladimír ČunátNo crashes since then so far. A huge improvement 🎉20:20:06
17 Feb 2025
@Ericson2314:matrix.orgJohn Ericson hexa (signing key rotation when): I have queued up a number of changes on master, and so I think it would be good to think about how to deploy 00:24:08
@Ericson2314:matrix.orgJohn Ericson we could jump to the front and bisect, but I think probably walking linearly through the --first-parent history is more prudent 00:24:31
@hexa:lossy.networkhexaI think bumping to HEAD on my private hydra would be a start00:25:27
@hexa:lossy.networkhexa
error:
       … while calling the 'attrNames' builtin
         at «string»:1:207:
            1| with builtins; let assets = getFlake "path:/tmp/nix-shell.sIGhyV/colmena-assets-EvihtE?lastModified=1739752075&narHash=sha256-yHR3T7GNYyN/b/GMe1oEW6j4S1EJqqfu9Hd/Me4imb4%3D"; hive = assets.processFlake; in attrNames hive.nodes
             |                                                                                                                                                                                                               ^

       … while calling the 'getFlake' builtin
         at «string»:1:29:
            1| with builtins; let assets = getFlake "path:/tmp/nix-shell.sIGhyV/colmena-assets-EvihtE?lastModified=1739752075&narHash=sha256-yHR3T7GNYyN/b/GMe1oEW6j4S1EJqqfu9Hd/Me4imb4%3D"; hive = assets.processFlake; in attrNames hive.nodes
             |                             ^

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: cannot update unlocked flake input 'hive' in pure mode
[ERROR] -----
[ERROR] Operation failed with error: Child process exited with error code: 1
00:28:04
@hexa:lossy.networkhexacool, have to debug why nix doesn't like my colmena flake anymore first 🙂 00:28:17
@hexa:lossy.networkhexahttps://github.com/zhaofengli/colmena/issues/25900:28:57
@hexa:lossy.networkhexaok00:46:54

Show newer messages


Back to Room ListRoom Version: 6