fix failing test vsock in checkbox provider #249
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
checkbox22/24 comes with the iperf3 package it will mask the iperf-vsock tool we install on the host this tool should be bundled in the snap
hector-cao
force-pushed
the
noble-24.04-fix-failing-test-iperf
branch
from
47f0fa0 to
88488e0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
vsock test uses a customized iperf tool with vsock support
this tool is installed on the host
however, checkbox24 comes with iperf tool and it will be used by the test,
without vsock support, the test fails
we device to bundle the customized iperf tool to the checkbox provider
and set PATH variable to use the iperf in the provider
one other solution would be to set the PATH to use the iperf installed on the system
but we think that bundle iperf3 into the provider is a better approach