[
https://issues.apache.org/jira/browse/CASSANDRA-20731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jane He updated CASSANDRA-20731:
--------------------------------
Description:
Investigating flaky tests
# `MetricsITBase.should_evict_down_node_metrics_when_timeout_fires` and
`MetricsITBase.should_not_evict_down_node_metrics_when_node_is_back_up_before_timeout`
lambda not satisfied.
## Suspect: the timeout threshold is not tolerant enough.
## Fix: Raise timeout thresholds.
# `PreparedStatementCachingIT` Latch not triggered before time out
## Suspect: the interval is not tolerant enough. Schema change statements tend
to take a long time to execute.
## Fix: `session.checkSchemaAgreement();` before assertions
# `UdtCodecIT``Query timed out after PT10S`
## Suspect: "CREATE TABLE" and "CREATE TYPE" timeout threshold not tolerant
enough.
## Fix: raise timeout threshold.
# `OsgiShadedIT.test_shaded`
`com.datastax.oss.driver.api.osgi.service.MailboxService not found by
PAXEXAM-PROBE-e72f8dd5-3084-4c86-9382-ca8b45cf1a68 [31]`
## Suspect: dependency resolution problem
## Fix: add start levels to bundle options
# `AddedNodeIT.should_signal_and_create_pool_when_node_gets_added` `TypeError:
Cluster.getNodeClass() got an unexpected keyword argument 'binary_interface'`
## Suspect: a bug in datastax/ccm, it was fixed
[here|https://github.com/apache/cassandra-ccm/commit/cbf0fd0ccb76d7a419763d10e806d73483a17c73]
## Fix: build and publish a new docker image with the updated ccm.
# `DefaultReactiveResultSetIT` query time out after PT10S
## Suspect: "DROP TABLE" timeout not tolerant enough
## Fix: raise timeout threshold
# `UuidsTest.should_generate_unique_random_uuids_Random`
should_generate_unique_random_uuids_Random`
## I couldn't figure out why. It does not fail that much anyway.
was:
Investigating flaky tests
# `MetricsITBase.should_evict_down_node_metrics_when_timeout_fires` and
`MetricsITBase.should_not_evict_down_node_metrics_when_node_is_back_up_before_timeout`
lambda not satisfied.
## Suspect: the timeout threshold is not tolerant enough.
## Fix: Raise timeout thresholds.
# `PreparedStatementCachingIT` Latch not triggered before time out
## Suspect: the interval is not tolerant enough. Schema change statements tend
to take a long time to execute.
## Fix: `session.checkSchemaAgreement();` before assertions
# `UdtCodecIT``Query timed out after PT10S`
## Suspect: "CREATE TABLE" and "CREATE TYPE" timeout threshold not tolerant
enough.
## Fix: raise timeout threshold.
# `OsgiShadedIT.test_shaded`
`com.datastax.oss.driver.api.osgi.service.MailboxService not found by
PAXEXAM-PROBE-e72f8dd5-3084-4c86-9382-ca8b45cf1a68 [31]`
## Suspect: dependency resolution problem
## Fix: add start levels to bundle options
# `AddedNodeIT.should_signal_and_create_pool_when_node_gets_added` `TypeError:
Cluster.getNodeClass() got an unexpected keyword argument 'binary_interface'`
## Suspect: a bug in datastax/ccm, it was fixed
[here|https://github.com/apache/cassandra-ccm/commit/cbf0fd0ccb76d7a419763d10e806d73483a17c73]
## Fix: build and publish a new docker image with the updated ccm.
> Fix Flaky Tests
> ---------------
>
> Key: CASSANDRA-20731
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20731
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Client/java-driver
> Reporter: Jane He
> Assignee: Jane He
> Priority: Normal
>
> Investigating flaky tests
> # `MetricsITBase.should_evict_down_node_metrics_when_timeout_fires` and
> `MetricsITBase.should_not_evict_down_node_metrics_when_node_is_back_up_before_timeout`
> lambda not satisfied.
> ## Suspect: the timeout threshold is not tolerant enough.
> ## Fix: Raise timeout thresholds.
> # `PreparedStatementCachingIT` Latch not triggered before time out
> ## Suspect: the interval is not tolerant enough. Schema change statements
> tend to take a long time to execute.
> ## Fix: `session.checkSchemaAgreement();` before assertions
> # `UdtCodecIT``Query timed out after PT10S`
> ## Suspect: "CREATE TABLE" and "CREATE TYPE" timeout threshold not tolerant
> enough.
> ## Fix: raise timeout threshold.
> # `OsgiShadedIT.test_shaded`
> `com.datastax.oss.driver.api.osgi.service.MailboxService not found by
> PAXEXAM-PROBE-e72f8dd5-3084-4c86-9382-ca8b45cf1a68 [31]`
> ## Suspect: dependency resolution problem
> ## Fix: add start levels to bundle options
> # `AddedNodeIT.should_signal_and_create_pool_when_node_gets_added`
> `TypeError: Cluster.getNodeClass() got an unexpected keyword argument
> 'binary_interface'`
> ## Suspect: a bug in datastax/ccm, it was fixed
> [here|https://github.com/apache/cassandra-ccm/commit/cbf0fd0ccb76d7a419763d10e806d73483a17c73]
> ## Fix: build and publish a new docker image with the updated ccm.
> # `DefaultReactiveResultSetIT` query time out after PT10S
> ## Suspect: "DROP TABLE" timeout not tolerant enough
> ## Fix: raise timeout threshold
> # `UuidsTest.should_generate_unique_random_uuids_Random`
> should_generate_unique_random_uuids_Random`
> ## I couldn't figure out why. It does not fail that much anyway.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
