[
https://issues.apache.org/jira/browse/CASSANDRA-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580629#comment-16580629
]
Patrick Bannister commented on CASSANDRA-14298:
-----------------------------------------------
[[email protected]], I built a CentOS system, checked out your copy of
CASSANDRA-14298, and ran some of the tests that failed on build 597. I have
LANG=en_US.utf8 and nothing set for LC_ALL or LC_CTYPE. Almost all of the
Unicode related tests passed:
* test_eat_glass
* test_source_glass
* test_unicode_syntax_error
* test_with_empty_values
* test_copy_to
I have two suggestions:
* Please check the output of locale -a on your test system and confirm that
you have an en_US.utf8 locale generated.
* If locale -a lists en_US.utf8 but not en_US.UTF-8, please try setting the
environment variable LANG=en_US.utf8.
Alternatively - is it possible for me to duplicate your Jenkins build and do
that troubleshooting myself? I haven't set up on Jenkins yet, but I'd be
willing to do it to work more efficiently on this ticket and eat up a little
less of your time.
Other failures...test_unicode_invalid_request_error fails for me too, but it
looks like a superficial problem. test_materialized_view looks like a more
substantive issue. I'll check into both.
> 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]
