#142 UDP CSV printout partially wrong

[Steffen Peter]

The CSV report output for UDP seems to be broken (at least on 32 bit ARM platforms). The last three numbers are wrong:

iperf -s -u -y C -i 5
20210915200510,127.0.0.1,5001,127.0.0.1,45783,4,0.0-5.0,322610610,516176976,0.001,3484,0,0.000,498739200
20210915200515,127.0.0.1,5001,127.0.0.1,45783,4,0.0-10.0,642861870,514329099,0.001,6362,0,0.000,384499972

the regular server report printout is correct:

[  3] Server Report:
[  3]  0.0-10.0 sec   613 MBytes   514 Mbits/sec   0.000 ms 6362/443683 (1.4%)

I suspect the reason is the reportCSV_bw_jitter_loss_format in Locale.c

Changing it from

const char reportCSV_bw_jitter_loss_format[] =
"%s,%s,%d,%.1f-%.1f,%" PRIdMAX ",%" PRIdMAX ",%.3f,%d,%d,%.3f,%d\n";

to

const char reportCSV_bw_jitter_loss_format[] =
"%s,%s,%d,%.1f-%.1f,%" PRIdMAX ",%" PRIdMAX ",%.3f,%" PRIdMAX ",%" PRIdMAX ",%.3f,%" PRIdMAX "\n";

solves the issue on my end

[Robert McMahon]

Thanks for this. I won't be able to get to it for a few weeks, i.e. towards the end of september

[Jean Tourrilhes]

Patch attached.

[Robert McMahon]

Patch applied & commited here. Will be part of the 2.1.9 release

[J O]

I have a similar issue but on the client side - CSV output iperf -y C -c 192.168.0.xxx always returns 1970/1/1 as timestamp: 19700101100000,192.168.0.xxx,41703,192.168.0.xxx,5001,1,0.0-10.0,1112670268,8872877541. It seems to work properly with 2.0.x versions.