!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

422 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.132 Servers

Load older messages


SenderMessageTime
19 Oct 2021
@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
@k900:0upti.meK900I have a PR that seemingly fixes it 18:40:29
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/pull/14220718:41:04
@janne.hess:helsinki-systems.deJanne Heßcan anyone restart the latest eval of the unstable-small jobsets?18:56:06
@janne.hess:helsinki-systems.deJanne Heß that's just the flakey test runner that K900 just fixed 18:56:21
@janne.hess:helsinki-systems.deJanne Heß * can anyone with enough permissions restart the latest eval of the unstable-small jobsets?18:56:33
@k900:0upti.meK900Can someone merge my PR before we restart anything?18:56:59
@k900:0upti.meK900Assuming everyone is OK with the changes18:57:07
@janne.hess:helsinki-systems.deJanne Heßeval takes time anyway18:57:10
@janne.hess:helsinki-systems.deJanne HeßThis eval: https://hydra.nixos.org/eval/171481918:57:15

Show newer messages


Back to Room ListRoom Version: 6