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.
This commit is contained in:
Marius Bakke 2022-09-11 22:59:41 +02:00
parent 9b3124b2fc
commit 752711b880
No known key found for this signature in database
GPG key ID: A2A06DF2A33A54FA

View file

@ -4984,12 +4984,17 @@ (define-public python-uvloop
;; The tests are prone to get stuck. Use pytest-timeouts --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.