!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

424 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.133 Servers

Load older messages


SenderMessageTime
19 Oct 2021
@k900:0upti.meK900I've never touched nixos infra before12:26:37
@janne.hess:helsinki-systems.deJanne Heßwe've seen that as well, restarting might help12:27:34
@janne.hess:helsinki-systems.deJanne HeßMaybe fixing that will also fix the test getting randomly stuck sometimes 🤔12:31:21
@grahamc:nixos.org@grahamc:nixos.orgwhat is the issue in that test?13:25:57
@janne.hess:helsinki-systems.deJanne Heß sorry, the testss 13:28:09
@janne.hess:helsinki-systems.deJanne Heß * sorry, the tests 13:28:15
@janne.hess:helsinki-systems.deJanne Heß

looks like (at least for us) they sometimes get stuck while reading the output of a command:

$ sudo py-spy dump --pid 3774992
Process 3774992: /nix/store/97w52ckcjnfiz89h3lh7zf1kysgfm2s8-python3-3.9.6/bin/python3 /nix/store/pnfqk9c4w65jwyp0fcskawp404r2lvim-nixos-test-driver/bin/.nixos-test-driver-wrapped
Python v3.9.6 (/nix/store/97w52ckcjnfiz89h3lh7zf1kysgfm2s8-python3-3.9.6/bin/python3.9)

Thread 0x7FFFF77EB340 (active)
    execute (.nixos-test-driver-wrapped:586)
    systemctl (.nixos-test-driver-wrapped:561)
    get_unit_info (.nixos-test-driver-wrapped:530)
    check_active (.nixos-test-driver-wrapped:509)
    retry (.nixos-test-driver-wrapped:193)
    wait_for_unit (.nixos-test-driver-wrapped:527)
    <module> (<string>:118)
    test_script (.nixos-test-driver-wrapped:1175)
    run_tests (.nixos-test-driver-wrapped:1179)
    <module> (.nixos-test-driver-wrapped:1304)
Thread 0x7FFFF61D1640 (active)
    process_serial_output (.nixos-test-driver-wrapped:918)
13:28:47
@k900:0upti.meK900It won't :(13:31:02
@k900:0upti.meK900It doesn't even touch that code13:31:06
@k900:0upti.meK900Oh no13:33:16
@k900:0upti.meK900 I've looked at how execute is implemented 13:33:23
@janne.hess:helsinki-systems.deJanne HeßI did that too and then went on doing anything to unsee that13:34:03
@k900:0upti.meK900i will not attempt to refactor the nixos test infra i will not attempt to refactor the nixos test infra i will not attempt to 13:34:36
@janne.hess:helsinki-systems.deJanne HeßI have also said that about switch-to-configuration when I was younger… it was a lot of pain but it paid off. So go for it 🙃13:36:20
@ncfavier:matrix.orgnf
In reply to @k900:0upti.me
I've looked at how execute is implemented
seems like it will fail to detect the magic string if it's split across chunks
16:53:23
@ncfavier:matrix.orgnfthat could cause things to hang that weren't supposed to16:53:39
@k900:0upti.meK900Or if the program ever outputs the magic string16:54:15
@k900:0upti.meK900Even by accident16:54:24
@ncfavier:matrix.orgnfyeah16:54:34
@ncfavier:matrix.orgnfthough that seems less likely16:54:58
20 Oct 2021
@domenkozar:matrix.orgDomen KožarThreading code in python test driver is iffy11:49:58
@hexa:lossy.networkhexaThe atexit handler together with the threading seems problematic16:39:01
@k900:0upti.meK900It's fine actually16:41:20
@k900:0upti.meK900atexit handlers run before threads are destroyed16:41:37
@k900:0upti.meK900 (which is how threading cleans up after itself, among other things) 16:41:44
@k900:0upti.meK900https://hydra.nixos.org/build/156403450/nixlog/298 it's broken again :(18:24:24
@hexa:lossy.networkhexa
Fatal Python error: _enter_buffered_busy: could not acquire lock for <_io.BufferedWriter name='<stderr>'> at interpreter shutdown, possibly due to daemon threads
18:37:59
@hexa:lossy.networkhexalogging thread likely wants to print, but the writer is closed due to thread shutdown18:38:17
@hexa:lossy.networkhexamaybe the last commit that touched that bit should be reverted18:38:36
@hexa:lossy.networkhexafailing tests that don't relate to the actual tests are annoying18:38:45

Show newer messages


Back to Room ListRoom Version: 6