You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Joel Knighton (JIRA)" <ji...@apache.org> on 2016/03/28 17:11:25 UTC
[jira] [Commented] (CASSANDRA-11445) dtest failure in
sslnodetonode_test.TestNodeToNodeSSLEncryption
[ https://issues.apache.org/jira/browse/CASSANDRA-11445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214298#comment-15214298 ]
Joel Knighton commented on CASSANDRA-11445:
-------------------------------------------
This was added in [CASSANDRA-9220] and committed very recently (only to trunk).
My guess is that the tests just aren't flagged to not be run on 2.2/3.0. They should only run on 3.6 and above.
> dtest failure in sslnodetonode_test.TestNodeToNodeSSLEncryption
> ---------------------------------------------------------------
>
> Key: CASSANDRA-11445
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11445
> Project: Cassandra
> Issue Type: Test
> Reporter: Philip Thompson
> Assignee: DS Test Eng
> Labels: dtest
>
> {{Invalid yaml. Please remove properties [require_endpoint_verification] from your cassandra.yaml}}
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/556/testReport/sslnodetonode_test/TestNodeToNodeSSLEncryption/ssl_wrong_hostname_no_validation_test
> Failed on CassCI build cassandra-2.2_dtest #556
> All of the sslnodetonodetests are failing on 2.2 and 3.0. I assume a ticket was committed that broke these tests by changing the appropriate yaml key?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)