On Mon, Feb 09, 2026 at 06:05:32PM +0000, Santiago Vila wrote:
FAILED
tests/asynctests/test_async_client.py::TestServiceClient::test_client_send
FAILED tests/test_client.py::TestServiceClient::test_client_send - AssertionE...
debbisect output:
bisection finished successfully
last good timestamp: 20260204T204043Z
first bad timestamp: 20260205T023937Z
the following packages differ between the last good and first bad timestamp:
libpython3.13-minimal:amd64 3.13.11-1+b1 -> 3.13.12-1
libpython3.13-stdlib:amd64 3.13.11-1+b1 -> 3.13.12-1
libpython3.14-minimal:amd64 3.14.2-1+b1 -> 3.14.3-1
libpython3.14-stdlib:amd64 3.14.2-1+b1 -> 3.14.3-1
python3.13 3.13.11-1+b1 -> 3.13.12-1
python3.13-minimal 3.13.11-1+b1 -> 3.13.12-1
python3.14 3.14.2-1+b1 -> 3.14.3-1
python3.14-minimal 3.14.2-1+b1 -> 3.14.3-1
(The tests now fail on both 3.13 and 3.14.)
Bisecting Python between 3.14.2 and 3.14.3 identifies
f17281741c623eefe364ae4d7fd643c44bffe208 as the first "bad" commit, i.e.
https://github.com/python/cpython/pull/142743. That fits with the
tracebacks.
Upstream is inactive, but based on this the patch should be fairly easy:
I think the tests just need to use `.reset_mock()` rather than setting
the `call_count` attribute to 0. I'll give that a try.
--
Colin Watson (he/him) [[email protected]]
