Staging | 393 Members | |
| Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen | 128 Servers |
| Sender | Message | Time |
|---|---|---|
| 19 Oct 2021 | ||
| I was able to just build it locally:
| 08:28:47 | |
| * I was able to just build it locally:
| 08:29:03 | |
| * I was able to just build it locally:
| 08:29:10 | |
| That's the store path hydra tries to build | 08:29:25 | |
| weird... | 08:30:17 | |
| I am on ZFS which I think the builders also use, not sure what else could cause system-specific failures | 08:31:48 | |
| maybe the filesystem is weird on the builders? | 08:31:53 | |
| ah | 08:31:57 | |
| can you try if cp 9.0 works for you? | 08:32:21 | |
| what do you mean? | 08:32:44 | |
| Can you use cp 9.0 on your zfs without specifying any additional flags? | 08:33:07 | |
| ./result/bin/cp: missing file operand Try './result/bin/cp --help' for more information. | 08:33:58 | |
| like that? | 08:34:00 | |
| no like really copying a file | 08:34:16 | |
| that does copy_file_range now, maybe zfs is not happy with that | 08:34:30 | |
| works fine for anything I've tried, might need some pathological case to trigger it | 08:35:23 | |
| I imagine we'd see a lot more breakage if typical cp usage was broken | 08:35:30 | |
| True that | 08:35:36 | |
| also, Arch uses 9.0 on core and they don't have any more patches than we have: https://github.com/archlinux/svntogit-packages/commit/f6e08690bc11a243918d5416558f48426bfb1f8e | 08:35:58 | |
| here is a similar failure: https://hydra.nixos.org/build/156087864/nixlog/2 argo and jx both segfaulted while dumping shell completions to a file however, I can only reproduce the jx failure locally, argo builds fine for me | 08:56:07 | |
| any chance you can strace that dump call? | 09:16:24 | |
| @nix { "action": "setPhase", "phase": "installPhase" } installing execve("/nix/store/mdrahngimfvh4m6cwgjdb0zs6y2g7fsr-jx-2.1.155/bin/jx", ["/nix/store/mdrahngimfvh4m6cwgjdb"..., "completion", "bash"], 0x7fffffffd360 /* 90 vars */) = 0 brk(NULL) = 0x5edb000 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x8} --- +++ killed by SIGSEGV (core dumped) +++ /nix/store/ckw39mx7sx2axnhms10z3i2xgrwspcq1-stdenv-linux/setup: line 87: 19683 Segmentation fault (core dumped) strace $out/bin/jx completion $shell > jx.$shell | 21:57:58 | |
| 20 Oct 2021 | ||
| That kind of doesn't seem related to the coreutils stuff since coreutils aren't used here⦠but since you bisected to that exact commit it somehow has to be | 06:50:10 | |
| Please check with coredumpctl what exactly crashed | 07:07:57 | |
| 21 Oct 2021 | ||
| sorry for not being able to tend for staging-next as I intended, other things are keeping me busy currently. | 11:00:12 | |
| 22 Oct 2021 | ||
In reply to @sandro:supersandro.deNever used coredumpctl before but coredumpctl debug didnt give any useful information | 01:19:26 | |
| (gdb) run Starting program: /nix/store/mb7ymizzmrynrcxfayckc6fcvym5k8hx-jx-2.1.155/bin/jx Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7fd00a5 in dl_main () from /nix/store/mij848h2x5wiqkwhg027byvmf9x3gx7y-glibc-2.33-50/lib/ld-linux-x86-64.so.2 (gdb) bt #0 0x00007ffff7fd00a5 in dl_main () from /nix/store/mij848h2x5wiqkwhg027byvmf9x3gx7y-glibc-2.33-50/lib/ld-linux-x86-64.so.2 #1 0x00007ffff7fe82fe in _dl_sysdep_start () from /nix/store/mij848h2x5wiqkwhg027byvmf9x3gx7y-glibc-2.33-50/lib/ld-linux-x86-64.so.2 #2 0x00007ffff7fce073 in _dl_start () from /nix/store/mij848h2x5wiqkwhg027byvmf9x3gx7y-glibc-2.33-50/lib/ld-linux-x86-64.so.2 #3 0x00007ffff7fcd058 in _start () from /nix/store/mij848h2x5wiqkwhg027byvmf9x3gx7y-glibc-2.33-50/lib/ld-linux-x86-64.so.2 #4 0x0000000000000001 in ?? () #5 0x00007fffffffc926 in ?? () #6 0x0000000000000000 in ?? () | 01:19:30 | |
| I noticed
I have 2 questions:
| 16:19:18 | |
| I'll fix them | 16:19:51 | |
| I think I did recent updates to them | 16:19:56 | |