Hi! I have created the patch for the Cassandra version 3.0.14 and trying to test it using the cassandra dtests.
Problem is - dtests deadlocks at some random tests, time and again - on unpatched 3.0.14 version of Cassandra. What I have done. I cloned the cassandra repository (origin http://git-wip-us.apache.org/repos/asf/cassandra.git), and checked out to tags/cassandra-3.0.14 - head is on f3e38cb638113c2a23855a104d6082da5bc10ddb. Then I have cloned the cassandra-dtest repo (origin git:// github.com/riptano/cassandra-dtest.git). Head is on 6843d76d0a85ad82edf889e8280b87786dc48486. I setup dtests according to this instructions: https://github.com/riptano/cassandra-dtest/blob/master/INSTALL.md In addition, I have setup JAVA8_HOME and JAVA_HOME variables to public jre of my 1.8.0_144 jdk. I start testing using this command: JAVA8_HOME=$JAVA8_HOME nosetests --with-flaky --with-xunit --xunit-file=out.xunit.xml --force-flaky --max-runs=3 --verbose --debug-log=err.debug.nose.txt 1> out.txt 2> err.txt I run the tests on x86_64 CentOS 7 with 7.6G of RAM. Problem symptoms: During the "normal" run (I have got only 1 "normal" run in 5 attempts), err.txt is updated constantly with name of the test recently completed, and in the end out.xunit.xml file appears, with test summary results. nosetests process exits. During the "problem" run tests stop progressing (err.txt was not modified for 10 hours), out.xunit.xml is not appearing, nosetests process runs. I killed java processes, but nothing changed for 2 hours - nosetests process still runs, but files are unchanged. Any help would be appreciated, Sergey
