You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--json should emit a single JSON object at the end of a test
Actual Behavior
--json emits two copies of the expected monolithic JSON object
Steps to Reproduce
Use --json output on a build of iperf3 from master after merging of PR #1677. That PR didn't cause the issue, but it uncovered this issue in the process of fixing other problems.
Possible Solution
Working on it. Basically I'm restructuring iperf_json_finish() and cleaning up some of the logic, as well as adding some locking in places that need it.
The text was updated successfully, but these errors were encountered:
Add locking around fprintf() calls in JSONStream_Output(). Probably
not needed at the moment given that this function can only be called
from the main thread, but added for consistency and possible future
usage.
Fixes#1688.
…#1688)
Add locking around fprintf() calls in JSONStream_Output(). Probably
not needed at the moment given that this function can only be called
from the main thread, but added for consistency and possible future
usage.
Context
Version of iperf3: iperf-3.16+
Hardware: x86_64
Operating system (and distribution, if any): any
Bug Report
--json
should emit a single JSON object at the end of a test--json
emits two copies of the expected monolithic JSON objectUse
--json
output on a build of iperf3 from master after merging of PR #1677. That PR didn't cause the issue, but it uncovered this issue in the process of fixing other problems.Working on it. Basically I'm restructuring
iperf_json_finish()
and cleaning up some of the logic, as well as adding some locking in places that need it.The text was updated successfully, but these errors were encountered: