37 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%3Aopen17 Servers

Load older messages

19 Oct 2021
@janne.hess:helsinki-systems.dedas_jcan you try if cp 9.0 works for you?08:32:21
@r-burns:matrix.orgRyan Burnswhat do you mean?08:32:44
@janne.hess:helsinki-systems.dedas_jCan you use cp 9.0 on your zfs without specifying any additional flags?08:33:07
@r-burns:matrix.orgRyan Burns./result/bin/cp: missing file operand Try './result/bin/cp --help' for more information. 08:33:58
@r-burns:matrix.orgRyan Burnslike that?08:34:00
@janne.hess:helsinki-systems.dedas_jno like really copying a file08:34:16
@janne.hess:helsinki-systems.dedas_jthat does copy_file_range now, maybe zfs is not happy with that08:34:30
@r-burns:matrix.orgRyan Burnsworks fine for anything I've tried, might need some pathological case to trigger it08:35:23
@r-burns:matrix.orgRyan BurnsI imagine we'd see a lot more breakage if typical cp usage was broken08:35:30
@janne.hess:helsinki-systems.dedas_jTrue that08:35:36
@janne.hess:helsinki-systems.dedas_jalso, Arch uses 9.0 on core and they don't have any more patches than we have: https://github.com/archlinux/svntogit-packages/commit/f6e08690bc11a243918d5416558f48426bfb1f8e08:35:58
@r-burns:matrix.orgRyan Burnshere 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 me08:56:07
@janne.hess:helsinki-systems.dedas_jany chance you can strace that dump call?09:16:24
@r-burns:matrix.orgRyan Burns@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.$shell21:57:58
20 Oct 2021
@janne.hess:helsinki-systems.dedas_jThat 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 be06:50:10
@sandro:supersandro.deSandroPlease check with coredumpctl what exactly crashed07:07:57
21 Oct 2021
@hexa:lossy.networkhexasorry 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
@r-burns:matrix.orgRyan Burns
In reply to @sandro:supersandro.de
Please check with coredumpctl what exactly crashed
Never used coredumpctl before but coredumpctl debug didnt give any useful information
@r-burns:matrix.orgRyan Burns(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 master can't be merged into staging-next for 2 packages:

  • both modified: pkgs/development/python-modules/jupyter-client/default.nix
  • both modified: pkgs/development/python-modules/jupyterlab-git/default.nix

I have 2 questions:

  1. How does it usually gets handled? Would normally an update author propose an valid merge as a pull request?
  2. Does anyone get alerted for these failures?
@jonringer:matrix.orgjonringerI'll fix them16:19:51
@jonringer:matrix.orgjonringerI think I did recent updates to them16:19:56
@qyliss:fairydust.spaceAlyssa Rosstrofi: usually it's fixed by somebody merging master into staging-next and pushing to staging-next.16:20:16
@qyliss:fairydust.spaceAlyssa Rossthere's alerting here: https://github.com/NixOS/nixpkgs/pull/10515316:20:33

How does it usually gets handled? Would normally an update author propose an valid merge as a pull request?>

ad-hoc'ly by committers

Does anyone get alerted for these failures?

individuals, no. Some one needs to inspect the actions

@trofi:matrix.orgtrofiAha, nice!16:22:27
@qyliss:fairydust.spaceAlyssa RossI just check the PR with the action messages whenever I'm bored. Not sure what other people's workflows are. :P 16:22:51
@jonringer:matrix.orgjonringerironically, those packages are broken until https://github.com/NixOS/nixpkgs/pull/142432 gets merged anyway17:15:26

There are no newer messages yet.

Back to Room List