[
https://issues.apache.org/jira/browse/CASSANDRA-17653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709341#comment-17709341
]
Andres de la Peña commented on CASSANDRA-17653:
-----------------------------------------------
It seems that {{InsertUpdateIfConditionTest}} and
{{InsertUpdateIfConditionCollectionsTest}} is still flaky, as reported in
CASSANDRA-18393. The new errors are of the form:
{code}
junit.framework.AssertionFailedError: 4.2.0-SNAPSHOT boolean:false
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$0(InsertUpdateIfConditionTest.java:68)
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:97)
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:91)
{code}
and:
{code}
unit.framework.AssertionFailedError: 4.2.0-SNAPSHOT boolean:false
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$1(InsertUpdateIfConditionTest.java:72)
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:97)
at
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:91)
{code}
Bisect points to this ticket as the one introducing the change on the error
messages:
* Before:
[commit|https://github.com/apache/cassandra/commit/89f3978dcde958fbad191b8cf628fd89ace64d7a]
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2803/workflows/dc769b19-b383-4332-92db-12e7e54a49fa]
* After:
[commit|https://github.com/apache/cassandra/commit/cc28e1a85e2e5760436030ca57667fa69d6de233]
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2804/workflows/5bec4990-05da-4879-b097-57116c30ba5b]
Bisection also shows that the original failures were introduced for the first
time by CASSANDRA-16930:
* Before:
[commit|https://github.com/apache/cassandra/commit/ce2a0a28bc9ca21e1fae29f2a38448a877db06c3]
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2807/workflows/e08f482a-40bd-4dfc-b322-353572717ada]
* After:
[commit|https://github.com/apache/cassandra/commit/fe9cff663b48fecdb964caaded2004e83a0c89f4]
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2808/workflows/a63798dd-1916-4ef6-9e4c-9962127fc66b]
> Fix flaky test -
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[0:
> clusterMinVersion=3.0]
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17653
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17653
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
> Reporter: Brandon Williams
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.1-beta1, 4.1.x
>
>
> {code}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$0(InsertUpdateIfConditionTest.java:64)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:90)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:84)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> https://ci-cassandra.apache.org/job/Cassandra-4.1/34/testReport/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/testConditionalUpdate_0__clusterMinVersion_3_0__3/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
