ci: Cleanup iperf3 tests#83
Conversation
- Start iperf3 service instead of using systemd run since this is the standard way to start the server. - Use iperf3-darwin since it provides additional info (RTT). With this changes the macos-15 test is successful: https://github.com/lima-vm/socket_vmnet/actions/runs/11980467424/job/33404783754 Signed-off-by: Nir Soffer <nirsof@gmail.com>
nirs
requested review from
AkihiroSuda,
balajiv113 and
jandubois
and removed request for
balajiv113
| - name: "Lima: vm1: iperf3 (host -> vm1)" | ||
| run: | | ||
| iperf3 -c "$(cat /tmp/vm1_ip)" | ||
| iperf3-darwin -c "$(cat /tmp/vm1_ip)" |
There was a problem hiding this comment.
How does this solve the macos-15 issue? 👀
There was a problem hiding this comment.
I don't think this solves the issue - just another cleanup to unify the way we run host to vm tests, used in test/perf.sh.
There was a problem hiding this comment.
But I can split the changes to check which change is the fix.
There was a problem hiding this comment.
Removed iperf3-darwin here:
283be46
macos-15-large run:
https://github.com/lima-vm/socket_vmnet/actions/runs/11980909877/job/33406141644
There was a problem hiding this comment.
Actually we don't use this is test/perf.sh - this the way I'm testing manually with vfkit, I need to update test/perf.sh.
There was a problem hiding this comment.
The job failed without iper3-darwin:
https://github.com/lima-vm/socket_vmnet/actions/runs/11980909877/job/33406141644
Maybe it uses different DNS resolver?
There was a problem hiding this comment.
Thanks, the test doesn't seem relying on DNS?
There was a problem hiding this comment.
Right, this must be something else.
By specifying memory and cpus in the vm yaml. Signed-off-by: Nir Soffer <nirsof@gmail.com>
2 participants
With these changes the macos-15-large test is successful: https://github.com/lima-vm/socket_vmnet/actions/runs/11980467424/job/33404783754