[ 
https://issues.apache.org/jira/browse/CASSANDRA-14975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ariel Weisberg updated CASSANDRA-14975:
---------------------------------------
    Fix Version/s: 4.0.x
                   3.11.x
                   3.0.x
           Status: Patch Available  (was: Open)

I got it done and I didn't have to skip any tests. I made a few bits of cqlsh 
python 3 compatible. If we want to move tests around it's a bit of an 
orthogonal concern to getting the tests we have running. You can move the 
working tests around wherever you want.

[dtest 
code|https://github.com/apache/cassandra-dtest/compare/master...aweisberg:14975?expand=1]
[trunk|https://github.com/apache/cassandra/compare/trunk...aweisberg:14975-trunk?expand=1]
[tests|https://circleci.com/gh/aweisberg/cassandra/tree/14975-trunk]

The trunk patch cherry-picks cleanly to 2.2, 3.0, and 3.11. I don't really want 
to change 2.2 so I am thinking of starting at 3.0. I'll test 3.0, and 3.11 
shortly.

> cqlsh dtests are not running in CircleCI
> ----------------------------------------
>
>                 Key: CASSANDRA-14975
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14975
>             Project: Cassandra
>          Issue Type: Test
>          Components: Test/dtest
>            Reporter: Ariel Weisberg
>            Assignee: Ariel Weisberg
>            Priority: Major
>             Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> Right now the dtests skip these tests because most don't pass. Originally 
> they weren't being collected because the test files end in_tests.py instead 
> of _test.py, but I fixed that by adding _tests.py to the list of recognized 
> patterns.
> Get them all running in CircleCI. Nothing special they will be part of the 
> existing dtest jobs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to