[
https://issues.apache.org/jira/browse/CASSANDRA-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646326#comment-16646326
]
Stefan Podkowinski commented on CASSANDRA-14298:
------------------------------------------------
My idea on how to integrate the cql tests are now basically to add them as an
extra build to the CircleCI work-flow and builds.apache.org. Builds run on
b.a.o are already constantly running into timeout issues and adding cqlsh tests
will make this worse. Also cqlsh related regressions should be more easily to
predict than others, so we should leave the decision to the dev to run or not
to run them.
Here's what needs to be done next:
* CASSANDRA-14713 - any Python version and environment issues should be easier
to address, once the docker image has been update
* CASSANDRA-14806 - improved CircleCI work-flow will introduce ad-hoc jobs
than needs to be manually triggered by the developer
* CASSANDRA-14298 - add new cqlsh build to work-flow, see
[WIP-14298|https://github.com/spodkowinski/cassandra/tree/WIP-14298] (requires
dtest update in
[WIP-14298|https://github.com/spodkowinski/cassandra-dtest/tree/WIP-14298])
I've tested running the cqlsh tests using the free CircleCI settings once and
[results|https://circleci.com/gh/spodkowinski/cassandra/563#tests/containers/0]
indicate that the resources (4GB mem) are probably not enough to make the tests
pass reliably. It would be nice if we could make the tests fit into the free
tier settings, as I wouldn't expect that we need complex virtual testing
topology, for the sake of testing cqlsh aspects.
> cqlshlib tests broken on b.a.o
> ------------------------------
>
> Key: CASSANDRA-14298
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14298
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Testing
> Reporter: Stefan Podkowinski
> Assignee: Patrick Bannister
> Priority: Major
> Labels: cqlsh, dtest
> Attachments: CASSANDRA-14298-old.txt, CASSANDRA-14298.txt,
> cqlsh_tests_notes.md
>
>
> It appears that cqlsh-tests on builds.apache.org on all branches stopped
> working since we removed nosetests from the system environment. See e.g.
> [here|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-trunk-cqlsh-tests/458/cython=no,jdk=JDK%201.8%20(latest),label=cassandra/console].
> Looks like we either have to make nosetests available again or migrate to
> pytest as we did with dtests. Giving pytest a quick try resulted in many
> errors locally, but I haven't inspected them in detail yet.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
