[
https://issues.apache.org/jira/browse/CASSANDRA-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780067#comment-16780067
]
Patrick Bannister commented on CASSANDRA-14298:
-----------------------------------------------
Here's what I think I see:
* In container #26, test_cqlsh.py passes
* In container #28, test_cqlsh_copy.py test_bulk_round_trip_blogposts fails
because some of the nodes of the ccm cluster wouldn't start
* In container #29, test_cqlsh_copy.py
test_bulk_round_trip_blogposts_with_max_connections fails because the ccm
cluster has problems with its virtual network
* In container #68, test_cqlsh_copy.py test_round_trip_with_rate_file fails
because expected and observed data don't match. This may be another
environmental resource issue - I think we get trouble when the environment is
too slammed to get data through at the desired rate
These tests pass for me when I run the cqlsh copy tests in isolation. I'm
thinking about breaking the resource intensive bulk round trip tests in the
cqlsh copy tests into a separate script, and marking them as resource
intensive. What options does our test infrastructure offer for dealing with
resource intensive tests? I know [[email protected]] had some long term plans
to improve the infrax to deal with this, but maybe we have some options right
now that we could exercise by restructuring the cqlsh tests a bit.
> 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, Legacy/Testing
> Reporter: Stefan Podkowinski
> Assignee: Patrick Bannister
> Priority: Major
> Labels: cqlsh, dtest, pull-request-available
> Attachments: CASSANDRA-14298.txt, cqlsh_tests_notes.md
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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]
