[jira] [Commented] (CASSANDRA-9369) HSHA dtest for closing connections is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551103#comment-14551103
]
Jonathan Ellis commented on CASSANDRA-9369:
---
+1
> HSHA dtest for closing connections is failing on trunk
> --
>
> Key: CASSANDRA-9369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9369
> Project: Cassandra
> Issue Type: Test
> Components: Tests
>Reporter: Tyler Hobbs
>Assignee: Ariel Weisberg
> Fix For: 2.2.x
>
> Attachments: 9369.diff
>
>
> The {{thrift_hsha_test.ThriftHSHATest.test_closing_connections}} dtest is
> failing against trunk (but not against 2.1). Here's an example failure:
> {noformat}
> Error Message
> There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME
> java28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-U0pP7H
> dtest: DEBUG: Creating connection pools..
> dtest: DEBUG: Disabling/Enabling thrift iteration #0
> dtest: DEBUG: Closing connections from the client side..
> pycassa.pool: INFO: Pool 13972199784 was disposed
> pycassa.pool: INFO: Pool 139721997714512 was disposed
> pycassa.pool: INFO: Pool 139721997749904 was disposed
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 331, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/thrift_hsha_test.py", line 59, in
> test_closing_connections
> self.assertEqual(len(lines), 0, "There are non-closed connections: %s" %
> stdout)
> File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual
> raise self.failureException(msg)
> 'There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME\njava28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)\n\n >> begin
> captured logging << \ndtest: DEBUG: cluster ccm
> directory: /tmp/dtest-U0pP7H\ndtest: DEBUG: Creating connection
> pools..\ndtest: DEBUG: Disabling/Enabling thrift iteration #0\ndtest: DEBUG:
> Closing connections from the client side..\npycassa.pool: INFO: Pool
> 13972199784 was disposed\npycassa.pool: INFO: Pool 139721997714512 was
> disposed\npycassa.pool: INFO: Pool 139721997749904 was
> disposed\n- >> end captured logging <<
> -'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9369) HSHA dtest for closing connections is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551061#comment-14551061
]
Philip Thompson commented on CASSANDRA-9369:
+1.
> HSHA dtest for closing connections is failing on trunk
> --
>
> Key: CASSANDRA-9369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9369
> Project: Cassandra
> Issue Type: Test
> Components: Tests
>Reporter: Tyler Hobbs
>Assignee: Ariel Weisberg
> Fix For: 2.2.x
>
> Attachments: 9369.diff
>
>
> The {{thrift_hsha_test.ThriftHSHATest.test_closing_connections}} dtest is
> failing against trunk (but not against 2.1). Here's an example failure:
> {noformat}
> Error Message
> There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME
> java28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-U0pP7H
> dtest: DEBUG: Creating connection pools..
> dtest: DEBUG: Disabling/Enabling thrift iteration #0
> dtest: DEBUG: Closing connections from the client side..
> pycassa.pool: INFO: Pool 13972199784 was disposed
> pycassa.pool: INFO: Pool 139721997714512 was disposed
> pycassa.pool: INFO: Pool 139721997749904 was disposed
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 331, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/thrift_hsha_test.py", line 59, in
> test_closing_connections
> self.assertEqual(len(lines), 0, "There are non-closed connections: %s" %
> stdout)
> File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual
> raise self.failureException(msg)
> 'There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME\njava28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)\n\n >> begin
> captured logging << \ndtest: DEBUG: cluster ccm
> directory: /tmp/dtest-U0pP7H\ndtest: DEBUG: Creating connection
> pools..\ndtest: DEBUG: Disabling/Enabling thrift iteration #0\ndtest: DEBUG:
> Closing connections from the client side..\npycassa.pool: INFO: Pool
> 13972199784 was disposed\npycassa.pool: INFO: Pool 139721997714512 was
> disposed\npycassa.pool: INFO: Pool 139721997749904 was
> disposed\n- >> end captured logging <<
> -'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9369) HSHA dtest for closing connections is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550640#comment-14550640
]
Ariel Weisberg commented on CASSANDRA-9369:
---
I don't think committers checking in dtests that they then comment out is a
related issue? Disabling tests willy nilly is not something I am advocating. If
that is going on it's not acceptable and I'm going to complain about it at the
retrospective.
It's broken. We know it. There is no more information to be gleaned. If you
comment it out it has to be filed and assigned to someone who isn't going to
blow it off. If you broke it you fix it and you don't get to merge.
If we keep known failing tests around it obscures new failures and causes
people to commit broken code to trunk because they think it works since the
tests don't pass anyways. There is no mechanism for diffing your results
against trunk to see if your subset of failures is different.
If the button isn't blue people need to know it's their problem and they can't
blow it off until they have addressed every last failure (to meet whatever our
definition of addressed/done is). And they have to know that if the do sneak it
into trunk, ignoring the failure or not having submitted it to Cassci at all,
that it isn't cool.
> HSHA dtest for closing connections is failing on trunk
> --
>
> Key: CASSANDRA-9369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9369
> Project: Cassandra
> Issue Type: Test
> Components: Tests
>Reporter: Tyler Hobbs
>Assignee: Ariel Weisberg
> Fix For: 2.2.x
>
>
> The {{thrift_hsha_test.ThriftHSHATest.test_closing_connections}} dtest is
> failing against trunk (but not against 2.1). Here's an example failure:
> {noformat}
> Error Message
> There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME
> java28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-U0pP7H
> dtest: DEBUG: Creating connection pools..
> dtest: DEBUG: Disabling/Enabling thrift iteration #0
> dtest: DEBUG: Closing connections from the client side..
> pycassa.pool: INFO: Pool 13972199784 was disposed
> pycassa.pool: INFO: Pool 139721997714512 was disposed
> pycassa.pool: INFO: Pool 139721997749904 was disposed
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 331, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/thrift_hsha_test.py", line 59, in
> test_closing_connections
> self.assertEqual(len(lines), 0, "There are non-closed connections: %s" %
> stdout)
> File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual
> raise self.failureException(msg)
> 'There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME\njava28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)\n\n >> begin
> captured logging << \ndtest: DEBUG: cluster ccm
> directory: /tmp/dtest-U0pP7H\ndtest: DEBUG: Creating connection
> pools..\ndtest: DEBUG: Disabling/Enabling thrift iteration #0\ndtest: DEBUG:
> Closing connections from the client side..\npycassa.pool: INFO: Pool
> 13972199784 was disposed\npycassa.pool: INFO: Pool 139721997714512 was
> disposed\npycassa.pool: INFO: Pool 139721997749904 was
> disposed\n- >> end captured logging <<
> -'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9369) HSHA dtest for closing connections is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550567#comment-14550567
]
Michael Shuler commented on CASSANDRA-9369:
---
Speaking for myself and my own workflow, the only way to see what tests are
failing is to run them continually in CI. CI is the tool I am using to track
the tests that are failing repeatedly, intermittently failing, or blowing up
everything. If they are hidden from my view and I don't see them fail in CI,
then they don't get brought to my attention. I volunteered to track the testing
to try to get to the goal of 100% passing, and I found this particular ticket
from a git commit message that caught my attention - not from the tool I am
using to track the state of testing, which is where I would like it.
As an example of the problem I have with disabling tests with {{@require}}, I
just now removed this disabling for CASSANDRA-8049 CASSANDRA-9300 and
CASSANDRA-9294 - the committers of those may or may not have known these dtests
were disabled, I don't know.
So I understand your point, but I would kindly request that you leave failing
tests to fail in CI. It is much easier for me to help with tracking the state
of tests.
> HSHA dtest for closing connections is failing on trunk
> --
>
> Key: CASSANDRA-9369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9369
> Project: Cassandra
> Issue Type: Test
> Components: Tests
>Reporter: Tyler Hobbs
>Assignee: Ariel Weisberg
> Fix For: 2.2.x
>
>
> The {{thrift_hsha_test.ThriftHSHATest.test_closing_connections}} dtest is
> failing against trunk (but not against 2.1). Here's an example failure:
> {noformat}
> Error Message
> There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME
> java28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-U0pP7H
> dtest: DEBUG: Creating connection pools..
> dtest: DEBUG: Disabling/Enabling thrift iteration #0
> dtest: DEBUG: Closing connections from the client side..
> pycassa.pool: INFO: Pool 13972199784 was disposed
> pycassa.pool: INFO: Pool 139721997714512 was disposed
> pycassa.pool: INFO: Pool 139721997749904 was disposed
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 331, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/thrift_hsha_test.py", line 59, in
> test_closing_connections
> self.assertEqual(len(lines), 0, "There are non-closed connections: %s" %
> stdout)
> File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual
> raise self.failureException(msg)
> 'There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME\njava28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)\n\n >> begin
> captured logging << \ndtest: DEBUG: cluster ccm
> directory: /tmp/dtest-U0pP7H\ndtest: DEBUG: Creating connection
> pools..\ndtest: DEBUG: Disabling/Enabling thrift iteration #0\ndtest: DEBUG:
> Closing connections from the client side..\npycassa.pool: INFO: Pool
> 13972199784 was disposed\npycassa.pool: INFO: Pool 139721997714512 was
> disposed\npycassa.pool: INFO: Pool 139721997749904 was
> disposed\n- >> end captured logging <<
> -'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9369) HSHA dtest for closing connections is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550496#comment-14550496
]
Ariel Weisberg commented on CASSANDRA-9369:
---
If we were caught up and all tests were passing then yes disabling failing
tests would be a no-no. Right now when we are far behind and trying to catch up
it makes sense to disable tests we know aren't passing.
See CASSANDRA-8997 and CASSANDRA-9002 for why (and feel free to comment and
disagree).
Discussing this might be good retrospective fodder. I want to bring up the fact
that it's been a few months and utests and dtests still aren't passing, and
people are still doing feature work. What's the point of doing feature work for
a system that you can't ship anyways because the tests don't pass? I wouldn't
be surprised if the tests don't pass by the time we want to ship 2.2. By
branching 2.2 we increased test load an complexity because now we have two
places to merge to and two sets of tests to monitor.
I don't agree with the thinking that addressing test issues delays feature
work. It's already delayed you are just in denial.
> HSHA dtest for closing connections is failing on trunk
> --
>
> Key: CASSANDRA-9369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9369
> Project: Cassandra
> Issue Type: Test
> Components: Tests
>Reporter: Tyler Hobbs
>Assignee: Ariel Weisberg
> Fix For: 2.2.x
>
>
> The {{thrift_hsha_test.ThriftHSHATest.test_closing_connections}} dtest is
> failing against trunk (but not against 2.1). Here's an example failure:
> {noformat}
> Error Message
> There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME
> java28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-U0pP7H
> dtest: DEBUG: Creating connection pools..
> dtest: DEBUG: Disabling/Enabling thrift iteration #0
> dtest: DEBUG: Closing connections from the client side..
> pycassa.pool: INFO: Pool 13972199784 was disposed
> pycassa.pool: INFO: Pool 139721997714512 was disposed
> pycassa.pool: INFO: Pool 139721997749904 was disposed
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 331, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/thrift_hsha_test.py", line 59, in
> test_closing_connections
> self.assertEqual(len(lines), 0, "There are non-closed connections: %s" %
> stdout)
> File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual
> raise self.failureException(msg)
> 'There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME\njava28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)\n\n >> begin
> captured logging << \ndtest: DEBUG: cluster ccm
> directory: /tmp/dtest-U0pP7H\ndtest: DEBUG: Creating connection
> pools..\ndtest: DEBUG: Disabling/Enabling thrift iteration #0\ndtest: DEBUG:
> Closing connections from the client side..\npycassa.pool: INFO: Pool
> 13972199784 was disposed\npycassa.pool: INFO: Pool 139721997714512 was
> disposed\npycassa.pool: INFO: Pool 139721997749904 was
> disposed\n- >> end captured logging <<
> -'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9369) HSHA dtest for closing connections is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550458#comment-14550458
]
Michael Shuler commented on CASSANDRA-9369:
---
Why are we disabling tests that happen to fail? Disabling failing tests from
the dtest suite only hides the failure from the people that want to see *all*
failures, disrupts viewing of test history in CI, and does not seem to have a
clear positive advantage.
In my opinion, there are only 2 reasons to disable a test:
1) The test completely hangs the test server.
2) A feature test is committed before the feature itself has been committed to
Cassandra.
> HSHA dtest for closing connections is failing on trunk
> --
>
> Key: CASSANDRA-9369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9369
> Project: Cassandra
> Issue Type: Test
> Components: Tests
>Reporter: Tyler Hobbs
>Assignee: Ariel Weisberg
> Fix For: 2.2.x
>
>
> The {{thrift_hsha_test.ThriftHSHATest.test_closing_connections}} dtest is
> failing against trunk (but not against 2.1). Here's an example failure:
> {noformat}
> Error Message
> There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME
> java28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-U0pP7H
> dtest: DEBUG: Creating connection pools..
> dtest: DEBUG: Disabling/Enabling thrift iteration #0
> dtest: DEBUG: Closing connections from the client side..
> pycassa.pool: INFO: Pool 13972199784 was disposed
> pycassa.pool: INFO: Pool 139721997714512 was disposed
> pycassa.pool: INFO: Pool 139721997749904 was disposed
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 331, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/thrift_hsha_test.py", line 59, in
> test_closing_connections
> self.assertEqual(len(lines), 0, "There are non-closed connections: %s" %
> stdout)
> File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual
> raise self.failureException(msg)
> 'There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME\njava28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)\n\n >> begin
> captured logging << \ndtest: DEBUG: cluster ccm
> directory: /tmp/dtest-U0pP7H\ndtest: DEBUG: Creating connection
> pools..\ndtest: DEBUG: Disabling/Enabling thrift iteration #0\ndtest: DEBUG:
> Closing connections from the client side..\npycassa.pool: INFO: Pool
> 13972199784 was disposed\npycassa.pool: INFO: Pool 139721997714512 was
> disposed\npycassa.pool: INFO: Pool 139721997749904 was
> disposed\n- >> end captured logging <<
> -'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9369) HSHA dtest for closing connections is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1459#comment-1459
]
Ariel Weisberg commented on CASSANDRA-9369:
---
Found it failing another way https://www.irccloud.com/pastebin/6GtHZQCt,
happened twice.
Also Tyler said the expected error is the one from this build (and I have seen
it before)
http://cassci.datastax.com/job/trunk_dtest/115/testReport/thrift_hsha_test/ThriftHSHATest/test_closing_connections/
> HSHA dtest for closing connections is failing on trunk
> --
>
> Key: CASSANDRA-9369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9369
> Project: Cassandra
> Issue Type: Test
> Components: Tests
>Reporter: Tyler Hobbs
>Assignee: Ariel Weisberg
> Fix For: 2.2.x
>
>
> The {{thrift_hsha_test.ThriftHSHATest.test_closing_connections}} dtest is
> failing against trunk (but not against 2.1). Here's an example failure:
> {noformat}
> Error Message
> There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME
> java28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-U0pP7H
> dtest: DEBUG: Creating connection pools..
> dtest: DEBUG: Disabling/Enabling thrift iteration #0
> dtest: DEBUG: Closing connections from the client side..
> pycassa.pool: INFO: Pool 13972199784 was disposed
> pycassa.pool: INFO: Pool 139721997714512 was disposed
> pycassa.pool: INFO: Pool 139721997749904 was disposed
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 331, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/thrift_hsha_test.py", line 59, in
> test_closing_connections
> self.assertEqual(len(lines), 0, "There are non-closed connections: %s" %
> stdout)
> File "/usr/lib/python2.7/unittest/case.py", line 515, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual
> raise self.failureException(msg)
> 'There are non-closed connections: COMMAND PID USER FD TYPE DEVICE
> SIZE/OFF NODE NAME\njava28202 automaton7u IPv4 60767 0t0 TCP
> localhost:58436->localhost:9160 (CLOSE_WAIT)\n\n >> begin
> captured logging << \ndtest: DEBUG: cluster ccm
> directory: /tmp/dtest-U0pP7H\ndtest: DEBUG: Creating connection
> pools..\ndtest: DEBUG: Disabling/Enabling thrift iteration #0\ndtest: DEBUG:
> Closing connections from the client side..\npycassa.pool: INFO: Pool
> 13972199784 was disposed\npycassa.pool: INFO: Pool 139721997714512 was
> disposed\npycassa.pool: INFO: Pool 139721997749904 was
> disposed\n- >> end captured logging <<
> -'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9369) HSHA dtest for closing connections is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542754#comment-14542754
]
Tyler Hobbs commented on CASSANDRA-9369:
I've disabled this test temporarily with the {{@require}} decorator.
> HSHA dtest for closing connections is failing on trunk
> --
>
> Key: CASSANDRA-9369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9369
> Project: Cassandra
> Issue Type: Test
> Components: Tests
>Reporter: Tyler Hobbs
>Assignee: Ariel Weisberg
> Fix For: 2.2.x
>
>
> The {{thrift_hsha_test.ThriftHSHATest.test_closing_connections}} dtest is
> failing against trunk (but not against 2.1). Here's an example failure:
> {noformat}
> ~/cassandra-dtest $ CASSANDRA_DIR=/home/thobbs/cassandra nosetests
> thrift_hsha_test.py:ThriftHSHATest.test_closing_connections
> F
> ==
> FAIL: test_closing_connections (thrift_hsha_test.ThriftHSHATest)
> --
> Traceback (most recent call last):
> File "/home/thobbs/cassandra-dtest/thrift_hsha_test.py", line 59, in
> test_closing_connections
> self.assertEqual(len(lines), 0, "There are non-closed connections: %s" %
> stdout)
> AssertionError: There are non-closed connections: lsof: WARNING: can't stat()
> ext4 file system /var/lib/docker/aufs
> Output information may be incomplete.
> >> begin captured logging <<
> dtest: DEBUG: Using jna.jar in CASSANDRA_DIR/lib..
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-lH_n0m
> cassandra.cluster: WARNING: [control connection] Error connecting to
> 127.0.0.1:
> Traceback (most recent call last):
> File "build/bdist.linux-x86_64/egg/cassandra/cluster.py", line 1892, in
> _reconnect_internal
> return self._try_connect(host)
> File "build/bdist.linux-x86_64/egg/cassandra/cluster.py", line 1909, in
> _try_connect
> connection = self._cluster.connection_factory(host.address,
> is_control_connection=True)
> File "build/bdist.linux-x86_64/egg/cassandra/cluster.py", line 710, in
> connection_factory
> return self.connection_class.factory(address, *args, **kwargs)
> File "build/bdist.linux-x86_64/egg/cassandra/io/libevreactor.py", line 242,
> in factory
> conn = cls(*args, **kwargs)
> File "build/bdist.linux-x86_64/egg/cassandra/io/libevreactor.py", line 277,
> in __init__
> raise socket.error(sockerr.errno, "Tried connecting to %s. Last error:
> %s" % ([a[4] for a in addresses], sockerr.strerror))
> error: [Errno 111] Tried connecting to [('127.0.0.1', 9042)]. Last error:
> Connection refused
> cassandra.cluster: ERROR: Control connection failed to connect, shutting down
> Cluster:
> Traceback (most recent call last):
> File "build/bdist.linux-x86_64/egg/cassandra/cluster.py", line 756, in
> connect
> self.control_connection.connect()
> File "build/bdist.linux-x86_64/egg/cassandra/cluster.py", line 1866, in
> connect
> self._set_new_connection(self._reconnect_internal())
> File "build/bdist.linux-x86_64/egg/cassandra/cluster.py", line 1901, in
> _reconnect_internal
> raise NoHostAvailable("Unable to connect to any servers", errors)
> NoHostAvailable: ('Unable to connect to any servers', {'127.0.0.1':
> error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection
> refused")})
> dtest: DEBUG: Creating connection pools..
> dtest: DEBUG: Disabling/Enabling thrift iteration #0
> dtest: DEBUG: Closing connections from the client side..
> pycassa.pool: INFO: Pool 140535693143568 was disposed
> pycassa.pool: INFO: Pool 140535693272016 was disposed
> pycassa.pool: INFO: Pool 140535710507920 was disposed
> - >> end captured logging << -
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
