[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
01/02: gnu: python-uvloop: Disable flaky test.
From: |
guix-commits |
Subject: |
01/02: gnu: python-uvloop: Disable flaky test. |
Date: |
Sun, 11 Sep 2022 17:46:10 -0400 (EDT) |
mbakke pushed a commit to branch master
in repository guix.
commit 752711b880f148ee7aab7a6ab8c3aaccdd8838de
Author: Marius Bakke <marius@gnu.org>
AuthorDate: Sun Sep 11 22:59:41 2022 +0200
gnu: python-uvloop: Disable flaky test.
* gnu/packages/python-web.scm (python-uvloop)[arguments]: Disable one more
test. While at it, use 'thread' timeout method as signal did not work here.
Also don't compute the pytest string at evaluation time.
---
gnu/packages/python-web.scm | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/python-web.scm b/gnu/packages/python-web.scm
index 4234b4bcab..94544e1e74 100644
--- a/gnu/packages/python-web.scm
+++ b/gnu/packages/python-web.scm
@@ -4984,12 +4984,17 @@ hard or impossible to fix in cssselect.")
;; The tests are prone to get stuck. Use pytest-timeout’s
--timeout
;; flag to get a meaningful idea about where.
(invoke "pytest" "-vv" "--timeout=300"
- "-k" ,(string-append
+ "--timeout-method=thread"
+ "-k" (string-append
;; Timeout, because SIGINT cannot be sent to
child.
"not test_signals_sigint_pycode_continue "
"and not test_signals_sigint_pycode_stop "
"and not test_signals_sigint_uvcode "
"and not
test_signals_sigint_uvcode_two_loop_runs "
+ ;; This test is racy and prone to get stuck on
+ ;; various platforms, possibly a aiohttp issue:
+ ;;
https://github.com/MagicStack/uvloop/issues/412
+ "and not
test_remote_shutdown_receives_trailing_data "
;; It looks like pytest is preventing
;; custom stdout/stderr redirection,
;; even with -s.