[
https://issues.apache.org/jira/browse/CASSANDRA-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780817#comment-16780817
]
Dinesh Joshi commented on CASSANDRA-14298:
------------------------------------------
[~ptbannister] I realized the CircleCI wasn't executing the tests as intended.
I made some minor modifications and reran only the cqlsh tests. There were 5
failures out of 99. Here are teh failures -
# test_colons_in_string_literals - cqlsh_tests.test_cqlsh.TestCqlshSmoke - test
teardown
# test_uuid - cqlsh_tests.test_cqlsh.TestCqlshSmoke - test teardown
# test_bulk_round_trip_blogposts - cqlsh_tests.test_cqlsh_copy.TestCqlshCopy -
assertion error
# test_bulk_round_trip_blogposts_with_max_connections - assertion error
# test_round_trip_with_rate_file - assertion error
We should definitely look into the assertions first. Individual test function
is being run in a 8 Core / 16GB container so I don't think they should be
resource constrained.
> 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]