-
Notifications
You must be signed in to change notification settings - Fork 173
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
Current version of netperf does not contain ppc64le support #1412
Comments
@ldoktor is it ok if I create PR with updated netperf with changes to all locations in testcases cfg to point to new version of it? |
That would be welcome, thank you for noticing this 😄 |
@ldoktor I have come across more generic approach for handling stress in utils_test [VMStress]. Which is better than having individual stress's in deps within avocado -> coyping to dest -> setup. I am in process of implementing this approach for netperf stress on ppc64le. |
OK, would you care to share some details when it's ready? :-) Also fixing nerperf might be good for the community so let me take that over... |
@ldoktor I am using recently added libraries @ avocado-vt/pull/1467.. I had sent uperf stress scenarios using same in tp-libvirt/pull/1680 .. For now I am implementing same approach in kdump_with_stress script for running netperf on ppc64le.. same can be reused as well for other archs.. |
I thought we can now start using generic apis to download/clone stress tools from hosted environment directly to place where it is required to run. If you are thinking that having the updated stress package to be part of deps would help, then I will pursue this issue and send the PR. |
Well hard to say. I prefer fetching from upstream, but this was changed quite recently in 11975c3 to download from our git (probably to save bandwidth and avoid external links? |
OK, I tried fixing it, but |
config.guess of either netperf-2.4.5 or netperf-2.6.0 does not include support for ppc64le. I see PR for same in netperf github @ HewlettPackard/netperf#6 .. but same is not updated in tp-qemu.
The text was updated successfully, but these errors were encountered: