[
https://issues.apache.org/jira/browse/PROTON-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118841#comment-17118841
]
Jiri Daněk commented on PROTON-1800:
------------------------------------
Test added, It used to pass for me so far, everywhere, but today I saw it fail
on an Ubuntu system.
{noformat}
======================================================================
FAIL: test_sync_request_response_blocking_connection_no_object_leaks
(test_PROTON_1800_syncrequestresponse_fd_leak.Proton1800Test)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/foo/proton/python/tests/integration/test_PROTON_1800_syncrequestresponse_fd_leak.py",
line 135, in test_sync_request_response_blocking_connection_no_object_leaks
client.connection.close()
File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
self.gen.next()
File
"/foo/proton/python/tests/integration/test_PROTON_1800_syncrequestresponse_fd_leak.py",
line 61, in no_fd_leaks
test.assertEqual(0, delta, "Found {0} new fd(s) after the
test".format(delta))
AssertionError: Found 1 new fd(s) after the test
{noformat}
Note that the test is wrongly named, it is looking for fd leaks, not object
leaks.
CC [~kpvdr], I was wrong about this one. I thought it is for a different issue
which was partially fixed.
> BlockingConnection descriptor leak
> ----------------------------------
>
> Key: PROTON-1800
> URL: https://issues.apache.org/jira/browse/PROTON-1800
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: proton-c-0.21.0
> Reporter: Andy Smith
> Assignee: Jiri Daněk
> Priority: Major
> Labels: leak, workaround
> Fix For: proton-c-future
>
> Attachments: sync_client.py
>
>
> Modified collectd python plugin from using persistent connection to
> connection per read. Following change, detected descriptor leak.
> Attached modification to sync_client.py exhibits the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
