[
https://issues.apache.org/jira/browse/CASSANDRA-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355084#comment-17355084
]
Ekaterina Dimitrova commented on CASSANDRA-16670:
-------------------------------------------------
Thanks [~bereng].
I took a quick look and I am wondering whether there was some drivers update?
Those were not failing up to now and now I see this:
//CC [~aholmber] and [~samt]
h3.
{code:java}
Error Message
An unexpected protocol error occurred on host localhost/127.0.0.1:46739. This
is a bug in this library, please report: Must not send frame with WARNING flag
for native protocol version < 4
Stacktrace
com.datastax.driver.core.exceptions.ProtocolError: An unexpected protocol error
occurred on host localhost/127.0.0.1:46739. This is a bug in this library,
please report: Must not send frame with WARNING flag for native protocol
version < 4 at
com.datastax.driver.core.exceptions.ProtocolError.copy(ProtocolError.java:66)
at
com.datastax.driver.core.exceptions.ProtocolError.copy(ProtocolError.java:27)
at
com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:35)
at
com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:293)
at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:58)
at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:45) at
org.apache.cassandra.cql3.CQLTester.executeNet(CQLTester.java:956) at
org.apache.cassandra.cql3.ViewComplexTest.testBaseTTLWithSameTimestampTest(ViewComplexTest.java:641)
Caused by: com.datastax.driver.core.exceptions.ProtocolError: An unexpected
protocol error occurred on host localhost/127.0.0.1:46739. This is a bug in
this library, please report: Must not send frame with WARNING flag for native
protocol version < 4
{code}
> Flaky ViewComplexTest, ViewFilteringTest and InsertUpdateIfConditionTest
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-16670
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16670
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> *ViewComplexTest*
> Flaky
> [test|https://ci-cassandra.apache.org/job/Cassandra-4.0/43/testReport/junit/org.apache.cassandra.cql3/ViewComplexTest/testPartialDeleteSelectedColumnWithoutFlush_3_/]
> and move back away from 'long' section.
> *InsertUpdateIfConditionTest* (CASSANDRA-16676)
> Fails
> [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/testListItem_2__clusterMinVersion_4_0_0_rc2_SNAPSHOT_/]
> with a timeout. We can see in the history it takes quite a while in
> [CI|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/history/]
> _but_ it takes just 1m locally. Probably due to constrained resources.
> Looking at the
> [individual|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/]
> test cases, for compression i.e., we can see 378 at an average of 1s each it
> can easily go over the timeout of 240s. Recommendation is to either move to
> 'long' section of to raise the timeout for the class for CI.
> *ViewFilteringTest*
> Move back from 'long' section
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
