Message ID | fa8914ba1e89d7031b31d6741fa2787e67bec8dd.1719249491.git.juli@incana.org |
---|---|
State | New |
Headers | show |
Series | [bug#71751] gnu: python-trio: Disable failing test. | expand |
I happened to be reading the NEWS file for Guile 3.0.10 when my system reconfigure failed, leading me to notice and fix this failing build. After submitting this bug, I returned to reading that file and noticed a mention of signal handling in child processes[1]. Could this be related to the present issue of signals at build time? -Juli [1] http://git.savannah.gnu.org/cgit/guile.git/tree/NEWS#n206
diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm index 9ad89b8c32e..341b0c6feaf 100644 --- a/gnu/packages/python-xyz.scm +++ b/gnu/packages/python-xyz.scm @@ -28882,6 +28882,7 @@ (define-public python-trio " and not test_for_leaking_fds" ;; Signals don’t work in the build sandbox. " and not test_open_signal_receiver" + " and not test_is_main_thread" ;; These try to raise KeyboardInterrupt which does not work ;; in the build environment. " and not test_ki_self"