We've been seeing a lot of similar string comparison problems recently
and have made some progress in minimizing them. Its ironic that this
problem is in the Printable tests which were supposed to be an
improvement to the situation<grin>. The NormalModel asFormatString()
uses ClusterBase.formatVector() which itself uses String.format(). In
this case I think I would choose to fix the tests since the formatString
*should* track the local language settings as its intended to be user
readable.
I suggest deleting the test class until I can get a patch in for the
tests, or just run mvn install -DskipTests=true. Actually, it would be
most useful to delete the class and see if there are any other tests
like that one to bite us.
Jeff
Sean Owen wrote:
Ah yeah that's it. The decimal and thousands separator are switched,
generally, in Spanish-speaking countries.
We should not be relying on any locale-specific number parsing or
formatting, and it's hard to see sometimes where that creeps in.
And/or, the test ought not be based on the string representation if
possible, but maybe that's not feasible here.
On Mon, Apr 5, 2010 at 10:01 PM, Christoph Hermann
<christoph.herm...@guschtel.de> wrote:
Am Montag, 5. April 2010 22:50:11 schrieb Robin Anil:
try increasing MAVEN heap size
export MAVEN_OPTS=-Xmx1024m
junit.framework.ComparisonFailure: format
expected:<nm{n=0 m=[1[.100, 2.200,3.300] sd=0.]75}>
but was:<nm{n=0 m=[1[,100, 2,200, 3,300] sd=0,]75}>
this looks more like a locale setting error to me.
what is your locale set to?
regards
Christoph
