[
https://issues.apache.org/jira/browse/CASSANDRA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16474:
----------------------------------------
Test and Documentation Plan: Full CI runs completed, follow up with smaller
test runs targetting cql/cqlsh.
Status: Patch Available (was: In Progress)
Both Circle and Apache CI look much better:
* On the JDK 8 pipeline, all python tests are now green with the exception of
one {{indev_3.x_to_indev_trunk}} upgrade test. Will check on this after merging
and open a new JIRA if necessary.
* On the JDK 8 pipeline, one in-jvm upgrade failure. Should be fixed by
CASSANDRA-16415, which landed in the meantime.
* On the JDK11 pipeline, one failing python dtest. Looks unrelated, I'll
follow up with a new JIRA.
The [python driver PR|https://github.com/datastax/python-driver/pull/1100] has
been merged and the {{cassandra-test}} branch updated, so python dtests in CI
should start to pass again now.
However, we also need to rebuild the {{cassandra-testing}} docker images as
the previously installed driver includes cython extension modules which don't
get rebuilt when tests are run. These
are causing some test failures as they don't include the latest driver fixes.
I've opened a PR to exclude the cython extensions from the base image
I've rebundled the {{cassandra-driver-internal-only}} lib in C* and once the
images are rebuilt & published, the last thing to do is to run a minimal set of
python dtest/cqlsh tests.
*Patches*
* [Cassandra Builds|https://github.com/apache/cassandra-builds/pull/37/files]
*
[Cassandra|https://github.com/beobal/cassandra/commit/4977bc44639dd8d3d7c1fc4b80b095076f2c5dbc]
(trivial)
> Multiple python dtest failures after promoting protocol v5 from beta
> --------------------------------------------------------------------
>
> Key: CASSANDRA-16474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16474
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Labels: protocolv5
> Fix For: 4.0-beta
>
>
> After making v5 the default for connections where a preferred protocol
> version is not specified, a number of python dtests are failing in CI
> environments.
> The issue appears to be with how the driver handles cases where the bytes
> read from the client socket doesn't constitute a complete frame (or to be
> more specific, the read buffer is exhausted whilst in the middle of reading a
> frame).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
