From: Juliana Sims via Guix-patches via <guix-patches@gnu.org>
To: 71751@debbugs.gnu.org
Cc: Juliana Sims <juli@incana.org>, Lars-Dominik Braun <lars@6xq.net>,
Marius Bakke <marius@gnu.org>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
Sharlatan Hellseher <sharlatanus@gmail.com>,
Tanguy Le Carrour <tanguy@bioneland.org>,
jgart <jgart@dismail.de>
Subject: [bug#71751] [PATCH] gnu: python-trio: Disable failing test.
Date: Mon, 24 Jun 2024 13:18:11 -0400 [thread overview]
Message-ID: <fa8914ba1e89d7031b31d6741fa2787e67bec8dd.1719249491.git.juli@incana.org> (raw)
Hello,
This test has begun failing, causing the build of python-trio to fail as well.
Oddly, there doesn't appear to be any change in the Trio code that should
trigger a new test failure, so this may not be the best solution. However, the
code for is_main_thread() relies on signals working properly, which, as the
adjacent comment points out, does not work at build time.
If anyone has a better idea of what's going on here and, therefore, how to fix
it, feel free to offer input or a better patch. In the meantime, this should get
python-trio and its dependants building again.
Thanks,
Juli
* gnu/packages/python-xyz.scm [arguments]: Disable failing test.
Change-Id: I8a066fd17654ce8b1dfb0411d8df621e0f45a63d
---
gnu/packages/python-xyz.scm | 1 +
1 file changed, 1 insertion(+)
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"
base-commit: ac105faf4ceb67468c7011505a07a67b0c1b045f
--
2.45.1
next reply other threads:[~2024-06-24 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 17:18 Juliana Sims via Guix-patches via [this message]
[not found] ` <handler.71751.B.171924974921821.ack@debbugs.gnu.org>
2024-06-24 17:29 ` [bug#71751] Acknowledgement ([PATCH] gnu: python-trio: Disable failing test.) Juliana Sims via Guix-patches via
2024-07-01 16:48 ` Juliana Sims via Guix-patches via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa8914ba1e89d7031b31d6741fa2787e67bec8dd.1719249491.git.juli@incana.org \
--to=guix-patches@gnu.org \
--cc=71751@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=juli@incana.org \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).