Unit test failures in XmlDataSourceTest

Description

I'm seeing the following CLDR Unit Test failures when running on Windows 10. Seem not to happen on any UNIX like platforms...:

XmlDataSourceTest {
TestBadElementNesting (0.037s) Passed
TestDoubleQuotesDisallowedAsAttributeValue (0.004s) Passed
TestNoDtdVersionPath (0.003s) Passed
TestSimple {
Error: (XmlDataSourceTest.java:98) : paths order: expected com.google.common.collect.RegularImmutableList<[//ldmlBCP47/keyword/key[@name="cf"]/type[@name="standard"], //ldmlBCP47/keyword/key[@name="cf"]/type[@name="account"], //ldmlBCP47/keyword/key[@name="cu"]/type[@name="adp"], //ldmlBCP47/keyword/key[@name="cu"]/type[@name="zar"], //ldmlBCP47/keyword/key[@name="tz"]/type[@name="adalv"], //ldmlBCP47/keyword/key[@name="tz"]/type[@name="fjsuv"]]>, got com.google.common.collect.RegularImmutableList<[//ldmlBCP47/keyword/key[@name="tz"]/type[@name="adalv"], //ldmlBCP47/keyword/key[@name="tz"]/type[@name="fjsuv"], //ldmlBCP47/keyword/key[@name="cf"]/type[@name="standard"], //ldmlBCP47/keyword/key[@name="cf"]/type[@name="account"], //ldmlBCP47/keyword/key[@name="cu"]/type[@name="adp"], //ldmlBCP47/keyword/key[@name="cu"]/type[@name="zar"]]>
Error: (XmlDataSourceTest.java:103) : paths order: expected com.google.common.collect.RegularImmutableList<[//ldmlBCP47/keyword/key[@name="cf"]/type[@name="standard"], //ldmlBCP47/keyword/key[@name="cf"]/type[@name="account"], //ldmlBCP47/keyword/key[@name="cu"]/type[@name="adp"], //ldmlBCP47/keyword/key[@name="cu"]/type[@name="zar"], //ldmlBCP47/keyword/key[@name="tz"]/type[@name="adalv"], //ldmlBCP47/keyword/key[@name="tz"]/type[@name="fjsuv"]]>, got com.google.common.collect.RegularImmutableList<[//ldmlBCP47/keyword/key[@name="tz"]/type[@name="adalv"], //ldmlBCP47/keyword/key[@name="tz"]/type[@name="fjsuv"], //ldmlBCP47/keyword/key[@name="cf"]/type[@name="standard"], //ldmlBCP47/keyword/key[@name="cf"]/type[@name="account"], //ldmlBCP47/keyword/key[@name="cu"]/type[@name="adp"], //ldmlBCP47/keyword/key[@name="cu"]/type[@name="zar"]]>
} (0.035s) FAILED (2 failure(s))
} (0.082s) FAILED (2 failure(s))
} (12.259s) FAILED (2 failure(s))

Just scanning through the code, I'm seeing a lot of '\n' where I'm wondering if System.lineSeparator() would be more appropriate.

xpath

None

locale

None

Status

Priority

major

Assignee

David Beaumont

Reporter

John Emmons

tracReporter

None

Reviewer

None

Labels

None

Components

Fix versions

phase

None