You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[SKIPPED] Unsupported for Apache Cassandra Version 3.0.8: Server version 3.10+ is required
[OK] CassandraTypesDurationTests.Integration_Cassandra_MixedValues (1937 ms)
When scylla cluster is set up via ccm (no matter the version of scylla), the ccm <node> version command always returns a 3.0.8 version. This version is probably hardcoded in nodetool (ccm <node> version command delegates it to nodetool). However, there is a way to print a scylla version using ccm. There is a ccm <node> versionfrombuild command which seems to display the correct version of scylla node.
We need to adjust the logic responsible for filtering out the tests based on Scylla/Cassandra version. Testing framework should be aware whether it's used against Cassandra or Scylla cluster, and then execute either ccm <node> version or ccm <node> versionfrombuild respectively. Minimal versions required for specific tests should be adjusted for scylla, because I believe that there is no 1:1 mapping between Scylla's and Cassandra's versions and some features were probably introduced in different versions.
The text was updated successfully, but these errors were encountered:
muzarski
changed the title
CI: some tests are unnecessary skipped when run against Scylla
CI: some tests are unnecessarily skipped when run against Scylla
Jul 24, 2024
A simple example are tests for
duration
cql type:When scylla cluster is set up via ccm (no matter the version of scylla), the
ccm <node> version
command always returns a3.0.8
version. This version is probably hardcoded innodetool
(ccm <node> version
command delegates it tonodetool
). However, there is a way to print a scylla version using ccm. There is accm <node> versionfrombuild
command which seems to display the correct version of scylla node.We need to adjust the logic responsible for filtering out the tests based on Scylla/Cassandra version. Testing framework should be aware whether it's used against Cassandra or Scylla cluster, and then execute either
ccm <node> version
orccm <node> versionfrombuild
respectively. Minimal versions required for specific tests should be adjusted for scylla, because I believe that there is no 1:1 mapping between Scylla's and Cassandra's versions and some features were probably introduced in different versions.The text was updated successfully, but these errors were encountered: