Issue45062
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2021-08-31 13:43 by vstinner, last changed 2022-04-11 14:59 by admin. This issue is now closed.
Messages (3) | |||
---|---|---|---|
msg400732 - (view) | Author: STINNER Victor (vstinner) * | Date: 2021-08-31 13:43 | |
PPC64LE RHEL8 Refleaks 3.9: https://buildbot.python.org/all/#/builders/482/builds/128 test test_asyncio failed -- Traceback (most recent call last): File "/home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/test/test_asyncio/test_sock_lowlevel.py", line 373, in test_huge_content_recvinto self.loop.run_until_complete( File "/home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/asyncio/base_events.py", line 642, in run_until_complete return future.result() File "/home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/test/test_asyncio/test_sock_lowlevel.py", line 366, in _basetest_huge_content_recvinto self.assertEqual(size, 0) AssertionError: 978216 != 0 Full output (reformatted for readability): --- 0:22:42 load avg: 10.83 [300/425/1] test_asyncio failed (1 failure) (22 min 40 sec) -- running: (...) beginning 6 repetitions 123456 Unknown child process pid 201442, will report returncode 255 Loop <_UnixSelectorEventLoop running=False closed=True debug=False> that handles pid 201442 is closed ... Unknown child process pid 240062, will report returncode 255 Loop <_UnixSelectorEventLoop running=False closed=True debug=False> that handles pid 240062 is closed . /home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/test/support/__init__.py:1468: ResourceWarning: unclosed <socket.socket fd=9, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('127.0.0.1', 35628)> gc.collect() ResourceWarning: Enable tracemalloc to get the object allocation traceback Task exception was never retrieved future: <Task finished name='Task-17758' coro=<BaseSelectorEventLoop.sock_sendall() done, defined at /home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/asyncio/selector_events.py:433> exception=ConnectionResetError(104, 'Connection reset by peer')> Traceback (most recent call last): File "/home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/asyncio/selector_events.py", line 462, in sock_sendall return await fut File "/home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/asyncio/selector_events.py", line 470, in _sock_sendall n = sock.send(view[start:]) ConnectionResetError: [Errno 104] Connection reset by peer test test_asyncio failed -- Traceback (most recent call last): File "/home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/test/test_asyncio/test_sock_lowlevel.py", line 373, in test_huge_content_recvinto self.loop.run_until_complete( File "/home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/asyncio/base_events.py", line 642, in run_until_complete return future.result() File "/home/buildbot/buildarea/3.9.cstratak-RHEL8-ppc64le.refleak/build/Lib/test/test_asyncio/test_sock_lowlevel.py", line 366, in _basetest_huge_content_recvinto self.assertEqual(size, 0) AssertionError: 978216 != 0 --- Moreover, test_huge_content_recvinto() seems to change the event loop policy without restoring it once done: --- 0:48:26 load avg: 1.00 Re-running test_asyncio in verbose mode (matching: test_huge_content_recvinto) beginning 6 repetitions 123456 test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.EPollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.PollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.SelectEventLoopTests) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.367s OK test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.EPollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.PollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.SelectEventLoopTests) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.363s OK test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.EPollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.PollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.SelectEventLoopTests) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.402s OK test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.EPollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.PollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.SelectEventLoopTests) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.338s OK test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.EPollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.PollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.SelectEventLoopTests) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.332s OK test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.EPollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.PollEventLoopTests) ... ok test_huge_content_recvinto (test.test_asyncio.test_sock_lowlevel.SelectEventLoopTests) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.384s OK ...... Warning -- asyncio.events._event_loop_policy was modified by test_asyncio Before: None After: <asyncio.unix_events._UnixDefaultEventLoopPolicy object at 0x7fff9de7a1e0> 1 test failed again: test_asyncio --- |
|||
msg414422 - (view) | Author: Kumar Aditya (kumaraditya) * | Date: 2022-03-03 11:02 | |
@vstinner This issue has not been happening on the CI recently so can this be marked as pending or even close it and reopen when it does fail? |
|||
msg414430 - (view) | Author: STINNER Victor (vstinner) * | Date: 2022-03-03 11:27 | |
I didn't see this failure recently, I just close the issue. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:59:49 | admin | set | github: 89225 |
2022-03-03 11:27:33 | vstinner | set | status: open -> closed resolution: out of date messages: + msg414430 stage: resolved |
2022-03-03 11:02:02 | kumaraditya | set | nosy:
+ kumaraditya messages: + msg414422 |
2021-09-01 00:01:37 | shihai1991 | set | nosy:
+ shihai1991 |
2021-08-31 13:45:41 | vstinner | set | title: test_asyncio: test_huge_content_recvinto() failed -> test_asyncio: test_huge_content_recvinto() failed on PPC64LE RHEL8 Refleaks 3.9 |
2021-08-31 13:43:37 | vstinner | create |