[
https://issues.apache.org/jira/browse/CASSANDRA-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866708#comment-15866708
]
Ariel Weisberg commented on CASSANDRA-13219:
--------------------------------------------
This merged forward cleanly, but just to make sure it compiles I had cassci run
the unit tests and dtests for 2.2, 3.0, and 3.11.
https://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-cassandra-2.2-testall/1/
https://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-cassandra-3.0-testall/1/
https://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-cassandra-3.11-testall/1/
The dtests failed when I started them initially:
https://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-cassandra-3.0-dtest/1/
{noformat}
[artifact:dependencies] Transferring 4K from central
[artifact:dependencies] Downloading:
commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.pom
from repository apache at
https://repository.apache.org/content/repositories/releases
Err:
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Aborted by : False
Logical operation result is FALSE
{noformat}
It's not clear why but I restarted one of them and that is running and seems
happy.
I'll wait for the one to pass and if that is good enough for review I'll commit.
https://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-cassandra-3.0-dtest/2/
> Cassandra.yaml now unicode instead of ascii after 13090
> -------------------------------------------------------
>
> Key: CASSANDRA-13219
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13219
> Project: Cassandra
> Issue Type: Bug
> Components: Configuration
> Reporter: Philip Thompson
> Assignee: Ariel Weisberg
> Priority: Minor
> Fix For: 2.2.9, 3.0.11, 3.11.0, 4.0
>
> Attachments: utf8-to-ascii_yaml.patch
>
>
> After CASSANDRA-13090, which was commit
> 5725e2c422d21d8efe5ae3bc4389842939553650, cassandra.yaml now has unicode
> characters, specifically
> [0xe2|http://utf8-chartable.de/unicode-utf8-table.pl?start=8320&number=128&names=2&utf8=0x].
> Previously, it was only ascii.
> This is an admittedly minor change, but it is breaking. It affects (at least)
> a subset of python yaml parsing tools (which is a large number of tools that
> use C*).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
