[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

triage of recent dtest failures

Hi all,

Now that the vote is on for the next releases, I've done an initial triage
of the failed dtest runs from 2.2, 3.0, and 3.11 (based on my circleci
runs). Below are the ten dtest failures I found most often (not exhaustive,
but representative), and I opened up corresponding jiras for them.

Let's see if we can get all the tickets assigned and analyzed. If in
researching, a test is indescribably flakey, that is valuble knowledge as
well. Being able to identify flakey tests and label them as such is step
forward, lacking a full fix. With these tickets, it might be that the test
needs to be corrected, and might not necessarily be a problem with
database. In some cases, it will be a problem in casandra, so please keep
that in mind.

Remember, fixing these tests helps *all* of us get to more stable and
reliable releases, and thus makes the database and project as a whole

Also, feel free to reach out to me with questions on these.



* test_describecluster_more_information_three_datacenters -
- versions: 3.11, 3.0, 2.2

* test_closing_connections - thrift_hsha_test.TestThriftHSHA
- versions: 3.11, 3.0, 2.2

* test_mutation_v5 - write_failures_test.TestWriteFailures
- versions: 3.11 only

* snapshot_test.TestArchiveCommitlog.*
- versions: apparently only 3.0

* test_decommissioned_node_cant_rejoin - topology_test.TestTopology
- versions: seen on 3.0, but may be more

* test_functional - global_row_key_cache_test.TestGlobalRowKeyCache
- versions: apparently only 3.0

* test_system_auth_ks_is_alterable - auth_test.TestAuth
- versions: 3.0 / 3.11

* test_failure_threshold_deletions - paging_test.TestPagingWithDeletions
-versions 3.11 only

* test_sstableofflinerelevel - offline_tools_test.TestOfflineTools
- versions 3.0 only

* test_alter_rf_and_run_read_repair & test_read_repair_chance -
- versions 2.2, 3.0