[
https://issues.apache.org/jira/browse/CASSANDRA-15934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-15934:
--------------------------------------
Fix Version/s: (was: 3.11.x)
(was: 4.x)
(was: 3.0.x)
(was: 2.2.x)
4.0-beta3
3.11.9
3.0.23
2.2.19
Since Version: 2.2.18
Source Control Link:
https://github.com/apache/cassandra/commit/3a29f77743e57d0fb5abd21fc03f9591f51a08ef
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
CI results:
2.2:
https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-15934-cassandra-2.2-64E27C2E-C7A3-44A8-8AB7-A6B61A886E54
3.0:
https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-15934-cassandra-3.0-64E27C2E-C7A3-44A8-8AB7-A6B61A886E54
3.11:
https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-15934-cassandra-3.11-64E27C2E-C7A3-44A8-8AB7-A6B61A886E54
trunk:
https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-15934-trunk-64E27C2E-C7A3-44A8-8AB7-A6B61A886E54
The added tests didn't fail in any branch so ignored 3.0+ test failures as they
are unrelated.
2.2 has a lot of test failures but all look to be the cql tests, which are
known broken in 2.2
> In-jvm dtests use -1 as timestamp for all writes that don't specify 'USING
> TIMESTAMP'
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15934
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 2.2.19, 3.0.23, 3.11.9, 4.0-beta3
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
