Skip to content

Conversation

kalyazin
Copy link
Contributor

Changes

  • do not rely on the logs to check that the API expectedly failed with "no space left on device"
  • disable API timing check

Reason

Since we deliberately create a condition of no space, it is not guaranteed that Firecracker is able to produce complete log messages.

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.

Since we deliberately create a condition of no space, it is not
guaranteed that Firecracker is able to produce complete log messages.
Use the API error message instead.

Signed-off-by: Nikita Kalyazin <[email protected]>
Since we deliberately create a condition of no space, it is not
guaranteed that Firecracker is able to produce complete log messages.

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

codecov bot commented Aug 19, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.41%. Comparing base (acb79a2) to head (5a3ef83).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5395   +/-   ##
=======================================
  Coverage   82.41%   82.41%           
=======================================
  Files         266      266           
  Lines       30571    30571           
=======================================
  Hits        25194    25194           
  Misses       5377     5377           
Flag Coverage Δ
5.10-c5n.metal 82.37% <ø> (ø)
5.10-m5n.metal 82.37% <ø> (-0.01%) ⬇️
5.10-m6a.metal 81.65% <ø> (-0.01%) ⬇️
5.10-m6g.metal 78.98% <ø> (ø)
5.10-m6i.metal 82.37% <ø> (-0.01%) ⬇️
5.10-m7a.metal-48xl 81.64% <ø> (+<0.01%) ⬆️
5.10-m7g.metal 78.98% <ø> (ø)
5.10-m7i.metal-24xl 82.34% <ø> (+<0.01%) ⬆️
5.10-m7i.metal-48xl 82.34% <ø> (ø)
5.10-m8g.metal-24xl 78.98% <ø> (-0.01%) ⬇️
5.10-m8g.metal-48xl 78.98% <ø> (ø)
6.1-c5n.metal 82.41% <ø> (ø)
6.1-m5n.metal 82.41% <ø> (-0.01%) ⬇️
6.1-m6a.metal 81.69% <ø> (-0.01%) ⬇️
6.1-m6g.metal 78.98% <ø> (ø)
6.1-m6i.metal 82.40% <ø> (-0.01%) ⬇️
6.1-m7a.metal-48xl 81.68% <ø> (-0.01%) ⬇️
6.1-m7g.metal 78.98% <ø> (ø)
6.1-m7i.metal-24xl 82.42% <ø> (ø)
6.1-m7i.metal-48xl 82.43% <ø> (+<0.01%) ⬆️
6.1-m8g.metal-24xl 78.98% <ø> (ø)
6.1-m8g.metal-48xl 78.98% <ø> (ø)

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 self-assigned this Aug 19, 2025
@kalyazin kalyazin added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Aug 19, 2025
@kalyazin kalyazin marked this pull request as ready for review August 19, 2025 12:58
@kalyazin kalyazin merged commit de58e7f into firecracker-microvm:main Aug 19, 2025
7 checks passed
@kalyazin kalyazin deleted the space branch August 19, 2025 14:50
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