Investigate why tests fail with the newest Cassandra and bring it back in the CI #633
Milestone
Comments
cvybhu
added a commit
to cvybhu/scylla-rust-driver
that referenced
this issue
Oct 19, 2023
In January the tests started failing on Cassandra `4.1`, so we pinned the cassandra version to `4.0.7`, which didn't have these problems. `4.0.7` is the version that we've been using in the CI since then. In the meantime there were new releases of `Cassandra`, at the moment the latest is `4.1.3`. Let's try to go back to the latest version, maybe the problems fixed themselves during the last nine months. Refs: scylladb#620 Refs: scylladb#629 Fixes: scylladb#633 Signed-off-by: Jan Ciolek <jan.ciolek@scylladb.com>
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently, we started having some weird errors when running tests with Cassandra. We found that downgrading the Cassandra version from 4.1 to 4.0.7 solved the problem of failing tests and unblocked the CI, but we still don't know what exactly causes those issues and whether they are caused by bugs in the driver, tests, or Cassandra itself.
We need to find the root cause and eventually switch back to using the latest Cassandra version.
Previous issue about failing CI: #620
The text was updated successfully, but these errors were encountered: