wit-go/networkQuality/networkQuality.go, branch v0.0.2Unnamed repository; edit this file 'description' to name the repository.
http://cgit.wit.com/wit-go/networkQuality/atom?h=v0.0.22024-01-29T15:15:24Z[Feature] Be more explicit about which part of the test was unstable2024-01-29T15:15:24ZWill Hawkinshawkinsw@obs.cr2024-01-29T15:15:24Zurn:sha1:343954285090861f84a26e9818e2e946f87b8d1f
When a test did not run to stability, tell the user which part of the
test was unstable.
Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
[Feature] Special RPM calculation semantics when test does not stabilize2024-01-29T14:50:19ZWill Hawkinshawkinsw@obs.cr2024-01-29T14:49:51Zurn:sha1:60b273e673b7af9b30bf439bb1a177ee339883ba
When the test does not stabilize (responsiveness), using only the most
recent MAD probes to calculate the provisional final RPM could leave us
with a very small number of samples. So, instead, use all the probe
measurements to do the calculation.
Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
[Bugfix] Do not advance the interval when stable2024-01-28T03:04:12ZWill Hawkinshawkinsw@obs.cr2024-01-28T03:04:12Zurn:sha1:59b565b068c007e0e99bfc382f32fda3bc0cfe6f
By advancing the stability algorithm's interval when the measurement is
complete, we incorrectly expelled one of those intervals from the RPM
calculation. As a result, the final RPM calculation did not include all
the probe measurements that factored into stability calculation.
Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
[Bugfix] Only probes collected during stable MAD count2024-01-27T01:46:05ZWill Hawkinshawkinsw@obs.cr2024-01-27T01:46:05Zurn:sha1:e60066f572464da3a6f55999a48b1d38cf6423d6
For calculating the final RPM, only those probes that are sent/received
during the stable MAD should count.
Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
[Bugfix] Continue Adding LGCs During Responsiveness Stabilization2024-01-20T00:40:11ZWill Hawkinshawkinsw@obs.cr2024-01-20T00:37:11Zurn:sha1:65b039e33717ee43620363704cb3daa304a5e724
The client was not continuing to add load-generating connections at each
stability-check interval (as called for by the spec).
Also, the client now properly obeys the `--rpm.id` option given on the
command line.
Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
Relabel Working-Conditions Effect2024-01-07T20:50:20ZWill Hawkinshawkinsw@obs.cr2024-01-07T20:43:48Zurn:sha1:c5e0bce882b049718692fbc5e43e01a3cdfb1f01
Change how the effect of the working conditions is calculated and
presented to the user.
Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
[Feature] Reformat test result output.2024-01-05T00:17:06ZWill Hawkinshawkinsw@obs.cr2024-01-04T00:11:10Zurn:sha1:218f2e6d235c4e947a04a39e4e09acde7675de6a[Feature] Support for testing upload/download in parallel2024-01-05T00:10:37ZWill Hawkinshawkinsw@obs.cr2023-12-14T00:56:03Zurn:sha1:f3990f950277c2f61e0e1811b4b8a81fc0219da4
Use the `--rpm.parallel` to test in parallel mode. The default testing
mode is serial.
Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
[Bugfix] Fix broken foreign probe data loggers2023-12-12T01:10:55ZWill Hawkinshawkinsw@obs.cr2023-12-12T01:09:35Zurn:sha1:72fc4da533a22172a858150c2a3d9d050d723bf2
Thanks to a few typos, foreign probes were not being properly logged
when data loggers were in use.
[Feature] Add support for L4S2023-07-25T04:20:31ZWill Hawkinshawkinsw@obs.cr2023-07-23T05:27:40Zurn:sha1:2cef6fe8cc06ee889c3eef0bf37166cb7813a8d5
Signed-off-by: Will Hawkins <hawkinsw@obs.cr>