Bad CSV output

[Gilles Duboscq]

Hello Julien,

Couldn't this just be some locale problem?
I see that you have a french version of MS Excel and in the french locale
of some softwares the value separator for CSV is a semicolon (this is true
for most locale where the coma is the decimal separator).

That being said there is definitely a discrepancy between the column names
and the column that are being output. In particular, I think the data rows
do not contain the advertised 95 and 99% mean errors but only one mean
error.

-Gilles


On Wed, Jan 8, 2014 at 11:56 AM, Julien Ponge <julien.ponge at insa-lyon.fr>wrote:

> Hi,
>
> I noticed that JMH generates bad CSV output.
>
> Here is a sample output generated on MacOSX on some benchmark. Don't pay
> attention to numbers and stuff, it's a dummy run in bad benchmarking
> conditions, the point was just to generate a CSV file.
>
> I posted some (temporary) screenshots at
> https://www.dropbox.com/sh/y4z84so4xvljqvb/WvkGiBUH78
>
> As you can see LibreOffice manages to understand the file. Both MS Excel
> and Apple Numbers see 1 big column.
>
> I am running the latest hg tip of JMH.
>
> Hope it helps!
>
> - Julien
>
>
>
>
>