Hi Stefan,
The dtests have been typically flaky but are more or less stable in the recent
past. We are working towards stabilizing them. For the dev workflow locally, I
typically end up running a subset of the dtests via the pytest runner. I am not
sure how others run it.
I believe CircleCI re
On 3/18/19 9:52 PM, Michael Shuler wrote:
> On 3/18/19 9:06 PM, Patrick Bannister wrote:
>> I recommend we pick the longest supported stable release available. That
>> would be Python 3.7, which is planned to get its last release in 2023, four
>> years from now.
>> - Python 3.5 was planned to get i
On 3/18/19 9:06 PM, Patrick Bannister wrote:
> I recommend we pick the longest supported stable release available. That
> would be Python 3.7, which is planned to get its last release in 2023, four
> years from now.
> - Python 3.5 was planned to get its last major release yesterday
> - Python 3.6 i
Hello, I'm resuming work on Python 3 support for cqlsh (CASSANDRA-10190).
As discussed before, the plan for this work is to get it working on Python
3 while keeping it compatible with Python 2.7.
I'd like to settle on a Python 3 release to be our officially supported
tested version. It would be bu
Hi,
I am running large and "simple" dtests (executed via
cassandra-builds/build-scripts/cassandra-dtest-pytest.sh) and I find myself
quite frustrated as I do not know if there are errors because tests are
flaky or there are legit issues which produced them.
It is "simple" to check it one by one w
