[ 
https://issues.apache.org/jira/browse/CASSANDRA-21130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054681#comment-18054681
 ] 

David Capwell commented on CASSANDRA-21130:
-------------------------------------------

Sad to see the failure count increase, but looks like it was due to me rebasing 
and trunk has more failing tests now =(

||Repo||Branch||Parent Branch||SHA||Status||
|https://github.com/dcapwell/cassandra.git|commit_remote_branch/CASSANDRA-21130-trunk-1A33186A-3BED-4226-BD7D-A95DFCB58BDC|trunk|09eab911d33ca652861a4f8c3acc18fd98936ee3|Unstable

Failed Builds:
||Build||Result||Reason||
| jvm-dtest-simulator         | fail | Test 
org.apache.cassandra.simulator.test.HarrySimulatorTest::test-_jdk11 had an 
error,Test org.apach |
| jvm-upgrade-dtests          | fail | Test 
org.apache.cassandra.distributed.upgrade.ClusterMetadataUpgradeHarryTest::mappertimedout
 had an |
| jvm-utests-latest           | fail | Test 
org.apache.cassandra.tools.nodetool.CompactionHistoryTest::testCompactionProperties[0:
 cmd=[com |
| jvm11-dtests                | fail | Test 
org.apache.cassandra.distributed.test.accord.AccordMoveTest::moveTest-_jdk11 
failed,Error parsi |
| jvm11-dtests-fuzz           | fail | Test 
org.apache.cassandra.fuzz.topology.AccordBootstrapTest::bootstrapFuzzTest-_jdk11
 failed         |
| jvm11-utests                | fail | Error parsing 
jvm11-utests/unitTestReports/TESTS-TestSuites.xml 'message'                     
       |
| jvm17-dtests                | fail | Test 
junit.framework.TestSuite::org.apache.cassandra.distributed.test.accord.MigrationFromAccordWrit
 |
| jvm17-dtests-fuzz           | fail | Test 
org.apache.cassandra.fuzz.topology.AccordBootstrapTest::bootstrapFuzzTest-_jdk17
 failed         |
| jvm17-utests                | fail | Test 
org.apache.cassandra.index.accord.RouteIndexTest::test-_jdk17 had an error      
                |
| python-dtests               | fail | Test 
materialized_views_test.TestMaterializedViews::materialized_views_test.py::TestMaterializedView
 |
| python-dtests-large         | fail | Test 
consistency_test.TestAccuracy::consistency_test.py::TestAccuracy::test_network_topology_strateg
 |
| python-dtests-latest        | fail | Test 
topology_test.TestTopology::topology_test.py::TestTopology::test_crash_during_decommission
 had  |
| python-upgrade-dtests       | fail | Test 
upgrade_tests.upgrade_through_versions_test.TestUpgrade_indev_5_0_x_To_indev_trunk::upgrade_tes
 |
| python-upgrade-dtests-large | fail | Test 
upgrade_tests.upgrade_through_versions_test.TestUpgrade_indev_4_0_x_To_indev_trunk::upgrade_tes
 |


> Fix flakey tests due to tests updating SSTable format dynamically
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-21130
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21130
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: CI
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: NA
>
>         Attachments: 
> ci_summary-trunk-09eab911d33ca652861a4f8c3acc18fd98936ee3.html, 
> result_details-trunk-09eab911d33ca652861a4f8c3acc18fd98936ee3.tar.gz
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> There are several tests that set the SSTable format for the test, but this is 
> a global field and a background compaction can read the format and make 
> different decisions; leading to flakey failures.
> The motivating issue is that the new compaction cursor logic checks that the 
> format is BIG and then enables, else it falls back to previous logic.  When 
> the test changes to BTI this can cause a race with compaction leading to type 
> cast issues.  
> Switching the format at runtime is currently not supported and something done 
> specifically by tests, so need to make sure tests do it in a safe way to make 
> CI stable.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to