[ https://issues.apache.org/jira/browse/CASSANDRA-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478940#comment-16478940 ]
Stefan Podkowinski commented on CASSANDRA-14298: ------------------------------------------------ The latest changes setting LC_CTYPE explicitly from the python code doesn't seem to do the trick ([CircleCI|https://circleci.com/gh/krummas/cassandra/485#tests/containers/25]). Adding {{LC_CTYPE="C.UTF-8"}} to the environment instead seems to be cleaner anyways. WDYT [~krummas]? As for your remarks regard the cqlshlib Python3 migration, maybe it's a good time to move this discussion to the -dev mailing list and discuss how we move on with the testing code in general? > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org