You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you use a PostgreSQL SaaS? If so, which? Can you reproduce
the issue with a local PostgreSQL install?: N/A, building the python-asyncpg package on Fedora Linux infrastructure
Python version: 3.12.0
Platform: Fedora Linux Rawhide, s390x architecture (only!)
Do you use pgbouncer?: No
Did you install asyncpg with pip?: No, I am the maintainer of the distribution package.
If you built asyncpg locally, which version of Cython did you use?: 0.29.35
Can the issue be reproduced under both asyncio and uvloop?: No, only asyncio.yes
This is new in 0.29.0. I don’t have any idea why it is happening.
I can’t reproduce this with PYTHONASYNCIODEBUG=1, nor can I reproduce it with USE_UVLOOP=1. I have now seen this on x86_64 with asyncio and PYTHONASYNCIODEBUG=1.
I don’t have interactive access to an s390x machine, but I am happy to run experiments or test proposed fixes by submitting package test builds on Fedora infrastructure. For the time being, I plan to simply skip this test on s390x.
=================================== FAILURES ===================================
________ TestExecuteMany.test_executemany_server_failure_during_writes _________
Traceback (most recent call last):
File "/usr/lib64/python3.12/unittest/case.py", line 58, in testPartExecutor
yield
File "/usr/lib64/python3.12/unittest/case.py", line 634, in run
self._callTestMethod(testMethod)
File "/usr/lib64/python3.12/unittest/case.py", line 589, in _callTestMethod
if method() is not None:
^^^^^^^^
File "/builddir/build/BUILDROOT/python-asyncpg-0.29.0-1.fc40.s390x/usr/lib64/python3.12/site-packages/asyncpg/_testbase/__init__.py", line 92, in wrapper
self.loop.run_until_complete(coro)
File "/usr/lib64/python3.12/asyncio/base_events.py", line 664, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/builddir/build/BUILD/asyncpg-0.29.0/tests/test_execute.py", line 215, in test_executemany_server_failure_during_writes
self.assertLess(pos, 128, 'should stop early')
File "/usr/lib64/python3.12/unittest/case.py", line 1257, in assertLess
self.fail(self._formatMessage(msg, standardMsg))
File "/usr/lib64/python3.12/unittest/case.py", line 715, in fail
raise self.failureException(msg)
AssertionError: 128 not less than 128 : should stop early
The text was updated successfully, but these errors were encountered:
musicinmybrain
changed the title
Test failure in test_executemany_server_failure_during_writes under asyncio on s390x only
Test failure in test_executemany_server_failure_during_writes
Nov 5, 2023
I edited the original report because I have now seen this on x86_64 with asyncio and PYTHONASYNCIODEBUG=1 on Fedora 39:
=================================== FAILURES ===================================
________ TestExecuteMany.test_executemany_server_failure_during_writes _________
Traceback (most recent call last):
File "/builddir/build/BUILD/asyncpg-0.29.0/tests/test_execute.py", line 215, in test_executemany_server_failure_during_writes
self.assertLess(pos, 128, 'should stop early')
File "/usr/lib64/python3.12/unittest/case.py", line 1257, in assertLess
self.fail(self._formatMessage(msg, standardMsg))
File "/usr/lib64/python3.12/unittest/case.py", line 715, in fail
raise self.failureException(msg)
AssertionError: 128 not less than 128 : should stop early
=============================== warnings summary ===============================
tests/test_adversity.py::TestConnectionLoss::test_pool_release_timeout
/usr/lib64/python3.12/asyncio/events.py:84: ResourceWarning: unclosed <socket.socket fd=19, family=2, type=1, proto=0, laddr=('127.0.0.1', 41479), raddr=('127.0.0.1', 49274)>
self._context.run(self._callback, *self._args)
Enable tracemalloc to get traceback where the object was allocated.
See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.
tests/test_adversity.py::TestConnectionLoss::test_pool_release_timeout
/usr/lib64/python3.12/asyncio/events.py:84: ResourceWarning: unclosed <socket.socket fd=12, family=2, type=1, proto=0, laddr=('127.0.0.1', 35146), raddr=('127.0.0.1', 47067)>
self._context.run(self._callback, *self._args)
Enable tracemalloc to get traceback where the object was allocated.
See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
FAILED tests/test_execute.py::TestExecuteMany::test_executemany_server_failure_during_writes
= 1 failed, 302 passed, 2 skipped, 1 deselected, 2 warnings in 153.72s (0:02:33) =
the issue with a local PostgreSQL install?: N/A, building the
python-asyncpg
package on Fedora Linux infrastructures390x
architecture (only!)uvloop?:
No, onlyyesasyncio
.This is new in 0.29.0. I don’t have any idea why it is happening.
I can’t reproduce this withI have now seen this onPYTHONASYNCIODEBUG=1
, nor can I reproduce it withUSE_UVLOOP=1
.x86_64
withasyncio
andPYTHONASYNCIODEBUG=1
.I don’t have interactive access to anI am happy to run experiments or test proposed fixes by submitting package test builds on Fedora infrastructure. For the time being, I plan to simply skip this tests390x
machine, buton.s390x
The text was updated successfully, but these errors were encountered: