No, not really. It's just that dtests currently expect same behaviour for
3.x and up.
On Wed, Sep 28, 2016 at 8:41 PM Aleksey Yeschenko
wrote:
> We had one accidental merge from 3.0 into 3.9 (looking at you, you know
> who you are), so could be.
>
> --
> AY
>
> On 28 September 2016 at 17:48:27,
We had one accidental merge from 3.0 into 3.9 (looking at you, you know who you
are), so could be.
--
AY
On 28 September 2016 at 17:48:27, Philip Thompson
(philip.thomp...@datastax.com) wrote:
That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
accidentally also merged i
Might be I have only made differentiation for trunk and 2.x.
I'll investigate and report on JIRA. Thanks for assigning.
On Wed, Sep 28, 2016 at 6:48 PM Philip Thompson <
philip.thomp...@datastax.com> wrote:
> That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
> accidentally
That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
accidentally also merged into 3.9?
On Wed, Sep 28, 2016 at 12:40 PM, Oleksandr Petrov <
oleksandr.pet...@gmail.com> wrote:
> LWTTester issues are leftovers from the bad merge in
> https://github.com/riptano/cassandra-dtest/pu
LWTTester issues are leftovers from the bad merge in
https://github.com/riptano/cassandra-dtest/pull/1214
I've rebased and currently re-running tests.
On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson <
philip.thomp...@datastax.com> wrote:
> Hi All,
>
> cassandra-3.9:
> ===
Hi All,
cassandra-3.9:
===
testall: All passed!
===
dtest: 4 failures
cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest
.test_round_trip_with_authentication
Flaky test, needs a Jira ticket
cql_tests.L
