Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Netperf: update netperf client to fix an error #3761

Merged
merged 1 commit into from
Jul 11, 2023

Conversation

leidwang
Copy link
Contributor

Currently, netperf can not start when vcpu>32, and our developer fix this bz in netperf, so we need to replace it.

ID:2218410

Currently, netperf can not start when vcpu>32, and
our developer fix this bz in netperf, so we need to
replace it.

Signed-off-by: Leidong Wang <[email protected]>
@leidwang
Copy link
Contributor Author

leidwang commented Jun 29, 2023

Test this patch with vcpu=40.

(1/1) Host_RHEL.m9.u2.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.netperf_stress_test.TCP_STREAM.host2guest.q35: PASS (252.91 s)
RESULTS : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB HTML : /root/avocado/job-results/job-2023-06-28T23.15-ba41283/results.html

@leidwang
Copy link
Contributor Author

Hi @yanglei-rh Could you please help to review this patch?
Please check the bz2218410 for details as I am not sure if it is suitable to add the details to github, thanks!

Hi @PaulYuuu Could you please help to review it from multi_arch side? Btw, this change will only affect windows test. Thanks!

@leidwang
Copy link
Contributor Author

Hi @PaulYuuu Could you please help to review it from multi_arch side? Btw, this change will only affect windows test. Thanks!

Copy link
Contributor

@PaulYuuu PaulYuuu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should only be for windows.

@PaulYuuu PaulYuuu merged commit c1e5005 into autotest:master Jul 11, 2023
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants