[ https://issues.apache.org/jira/browse/CASSANDRA-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777662#comment-16777662 ]
Dinesh Joshi commented on CASSANDRA-14298: ------------------------------------------ [~ptbannister] I have gone over the changes and they look reasonable so I ran the dtests against trunk and few cqlsh tests have failed. Take a look [here|https://circleci.com/workflow-run/6426fd6f-0e35-4c0b-ba16-aeb3fb9a4247]. Could you please look into those failures? I believe a couple might be because the cluster failed to start. However others seem to be genuine. > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org