Skip to content

Conversation

kalyazin
Copy link
Contributor

@kalyazin kalyazin commented Sep 3, 2025

Changes

Move the copy into the test construction to copy the binary only once.

Reason

Currently we copy the iperf3-vsock binary into the guest in spawn_iperf3_client that is called by every client (we have 2). If by the time the second binary is being copied that first one is already executing, we get the "Text file busy" error.

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • [ ] I have run tools/devtool checkbuild --all to verify that the PR passes
    build checks on all supported architectures.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • [ ] I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • [ ] I have mentioned all user-facing changes in CHANGELOG.md.
  • [ ] If a specific issue led to this PR, this PR closes the issue.
  • [ ] When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • [ ] I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • [ ] I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

Problem: Currently we copy the iperf3-vsock binary into the guest in
spawn_iperf3_client that is called by every client (we have 2).  If by
the time the second binary is being copied that first one is already
executing, we get the "Text file busy" error.

Solution: Move the copy into the test construction to copy the binary
only once.

Signed-off-by: Nikita Kalyazin <[email protected]>
Copy link

codecov bot commented Sep 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.73%. Comparing base (286aa17) to head (a35f205).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5430   +/-   ##
=======================================
  Coverage   82.73%   82.73%           
=======================================
  Files         263      263           
  Lines       27455    27455           
=======================================
  Hits        22715    22715           
  Misses       4740     4740           
Flag Coverage Δ
5.10-m5n.metal 82.83% <ø> (-0.01%) ⬇️
5.10-m6a.metal 82.09% <ø> (-0.01%) ⬇️
5.10-m6g.metal 79.52% <ø> (ø)
5.10-m6i.metal 82.83% <ø> (ø)
5.10-m7a.metal-48xl 82.08% <ø> (-0.01%) ⬇️
5.10-m7g.metal 79.52% <ø> (ø)
5.10-m7i.metal-24xl 82.81% <ø> (-0.01%) ⬇️
5.10-m7i.metal-48xl 82.81% <ø> (-0.01%) ⬇️
5.10-m8g.metal-24xl 79.52% <ø> (ø)
5.10-m8g.metal-48xl 79.52% <ø> (ø)
6.1-m5n.metal 82.88% <ø> (ø)
6.1-m6a.metal 82.12% <ø> (-0.01%) ⬇️
6.1-m6g.metal 79.51% <ø> (-0.01%) ⬇️
6.1-m6i.metal 82.87% <ø> (-0.01%) ⬇️
6.1-m7a.metal-48xl 82.12% <ø> (ø)
6.1-m7g.metal 79.52% <ø> (ø)
6.1-m7i.metal-24xl 82.88% <ø> (-0.01%) ⬇️
6.1-m7i.metal-48xl 82.87% <ø> (-0.02%) ⬇️
6.1-m8g.metal-24xl 79.52% <ø> (-0.01%) ⬇️
6.1-m8g.metal-48xl 79.52% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@kalyazin kalyazin marked this pull request as ready for review September 3, 2025 16:55
@kalyazin kalyazin self-assigned this Sep 3, 2025
@kalyazin kalyazin added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Sep 3, 2025
@kalyazin kalyazin merged commit 1bd63b2 into firecracker-microvm:main Sep 4, 2025
8 checks passed
@kalyazin kalyazin deleted the vsock_bin branch September 4, 2025 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Status: Awaiting review Indicates that a pull request is ready to be reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants