hazelcast / hazelcast/hazelcast-python-client
Flaky test [Windows] ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_hostname_client_hostname [API-2340]
- Lingua principale
- Python
- Stelle
- 116
- Fork
- 78
- Merge medio
- 10g 22h
- PR unite (30g)
- 1
Descrizione
This test seems to fail only on Windows with Python 3.13.
Test report:
https://github.com/hazelcast/hazelcast-python-client/actions/runs/20095494138/job/57652771802#step:10:13975
Log:
```
ERROR asyncio:base_events.py:1879 Exception in callback _ProactorBasePipeTransport._call_connection_lost(OSError(10057..., 10057, None))
handle:
source_traceback: Object created at (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\runners.py", line 118, in run
return self._loop.run_until_complete(task)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 712, in run_until_complete
self.run_forever()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 683, in run_forever
self._run_once()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 2042, in _run_once
handle._run()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\events.py", line 89, in _run
self._context.run(self._callback, *self._args)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 316, in _loop_reading
self._fatal_error(exc, 'Fatal read error on pipe transport')
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 132, in _fatal_error
self._force_close(exc)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 152, in _force_close
self._loop.call_soon(self._call_connection_lost, exc)
Traceback (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\events.py", line 89, in _run
self._context.run(self._callback, *self._args)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 165, in _call_connection_lost
self._sock.shutdown(socket.SHUT_RDWR)
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
OSError: [WinError 10057] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied
INFO hazelcast.internal.asyncio_connection:asyncio_connection.py:1015 closed. Reason: Connection closed by server
WARNING hazelcast.internal.asyncio_connection:asyncio_connection.py:581 Error during initial connection to Member [localhost]:5701 - f70c836b-be1f-4c32-acbd-49017530ceca
Traceback (most recent call last):
File "D:\a\hazelcast-python-client\hazelcast-python-client\hazelcast\internal\asyncio_connection.py", line 576, in _connect
return await get_or_connect_func(target)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\a\hazelcast-python-client\hazelcast-python-client\hazelcast\internal\asyncio_connection.py", line 404, in _get_or_connect_to_member
await self._on_auth(response, connection)
File "D:\a\hazelcast-python-client\hazelcast-python-client\hazelcast\internal\asyncio_connection.py", line 624, in _on_auth
raise e
File "D:\a\hazelcast-python-client\hazelcast-python-client\hazelcast\internal\asyncio_connection.py", line 620, in _on_auth
response = await response
^^^^^^^^^^^^^^
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_hostname_client_hostname e il report CI di Windows collegato. Ispeziona hazelcast/internal/asyncio_connection.py intorno alle righe 576 e 620-624, insieme al traceback di asyncio di Python 3.13. Il lavoro è completato quando il test non fallisce più sporadicamente su Windows e la sua asserzione sul numero di connessioni passa in modo affidabile.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- python
- Ambito
- testing
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100