Re: cassandra-2.1 testing

On 04/08/2014 04:04 PM, Michael Shuler wrote: On 04/08/2014 03:50 PM, Jonathan Ellis wrote: How many of these are bisect-able? Many are test implementation errors, and may not be directly related to c* errors. They may need to be fixed in ccm or the dtest is just wrong. I'll keep after these t

Re: cassandra-2.1 testing

Thanks Mikhail, I remember I fixed this in ccm, but then I forgot that cqlsh_tests wasn't using the ccm api for invoking that. On Tue, Apr 8, 2014 at 5:54 PM, Mikhail Stepura wrote: > I suspect cqlsh-related tests a

Re: cassandra-2.1 testing

I suspect cqlsh-related tests are failing because cqlsh was trying to connect to 9160 (thrift) Could someone verify if switching to ‘binary’ solves this problem? Here is the patch: https://github.com/Mishail/cassandra-dtest/commit/33d648066df3f34a42035397fb366540784b6139 https://issues.apache

Re: cassandra-2.1 testing

On 04/08/2014 03:50 PM, Jonathan Ellis wrote: How many of these are bisect-able? Many are test implementation errors, and may not be directly related to c* errors. They may need to be fixed in ccm or the dtest is just wrong. I'll keep after these tickets, and bisect c* for ones that look like

Re: cassandra-2.1 testing

How many of these are bisect-able? On Tue, Apr 8, 2014 at 3:47 PM, Michael Shuler wrote: > Here is the current state of unit and dtest results for the cassandra-2.1 > branch, from the commit I started with this morning. > > origin/cassandra-2.1 > commit 0fa5cba35b9c97ad34dedbbd89a933f5b9d156e9 >

cassandra-2.1 testing

Here is the current state of unit and dtest results for the cassandra-2.1 branch, from the commit I started with this morning. origin/cassandra-2.1 commit 0fa5cba35b9c97ad34dedbbd89a933f5b9d156e9 Date: Tue Apr 8 12:26:09 2014 -0500 Unit Tests Failing: or