Open bltierney opened 4 months ago
When I use the -J flag with iperf3.17, I get 2 complete, identical copies of the JSON object (which unfortunately break the python JSON parser).
I dont see this happening with iperf3.15, so the bug might have something to do with the new threaded version?
(note: I see this with just 1 stream)
I don't see this issue using the tip of master. This sounds familiar, though, so I think there was a similar bug.
This is the issue report: https://github.com/esnet/iperf/issues/1688
When I use the -J flag with iperf3.17, I get 2 complete, identical copies of the JSON object (which unfortunately break the python JSON parser).
I dont see this happening with iperf3.15, so the bug might have something to do with the new threaded version?
(note: I see this with just 1 stream)