Skip to content

Conversation

bchalios
Copy link
Contributor

@bchalios bchalios commented Jul 29, 2025

Changes

Add some tolerance (1%) to the memory size check of test_serial_io.py::test_serial_dos to avoid false positives.

Reason

test_serial_dos ensures that the internal FIFO buffer used for storing the bytes to be written does not grow indefinitely. Some times during the test we observe small allocations that make the assertion fail.

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.

test_serial_dos ensures that the internal FIFO buffer used for storing
the bytes to be written does not grow indefinitely. Some times during
the test we observe small allocations that make the assertion fail.
Add some tolerance to the test (1%) to avoid false positives.

Signed-off-by: Babis Chalios <[email protected]>
@bchalios bchalios added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Jul 29, 2025
Copy link

codecov bot commented Jul 29, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.03%. Comparing base (304c393) to head (d6b4030).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5333      +/-   ##
==========================================
+ Coverage   82.98%   83.03%   +0.05%     
==========================================
  Files         250      250              
  Lines       26837    26837              
==========================================
+ Hits        22271    22285      +14     
+ Misses       4566     4552      -14     
Flag Coverage Δ
5.10-c5n.metal 83.48% <ø> (ø)
5.10-m5n.metal 83.48% <ø> (ø)
5.10-m6a.metal 82.70% <ø> (ø)
5.10-m6g.metal 79.15% <ø> (ø)
5.10-m6i.metal 83.48% <ø> (ø)
5.10-m7a.metal-48xl 82.69% <ø> (?)
5.10-m7g.metal 79.15% <ø> (ø)
5.10-m7i.metal-24xl 83.44% <ø> (?)
5.10-m7i.metal-48xl 83.44% <ø> (?)
5.10-m8g.metal-24xl 79.14% <ø> (?)
5.10-m8g.metal-48xl 79.14% <ø> (?)
6.1-c5n.metal 83.53% <ø> (ø)
6.1-m5n.metal 83.53% <ø> (ø)
6.1-m6a.metal 82.75% <ø> (+<0.01%) ⬆️
6.1-m6g.metal 79.15% <ø> (ø)
6.1-m6i.metal 83.53% <ø> (ø)
6.1-m7a.metal-48xl 82.74% <ø> (?)
6.1-m7g.metal 79.15% <ø> (ø)
6.1-m7i.metal-24xl 83.54% <ø> (?)
6.1-m7i.metal-48xl 83.55% <ø> (?)
6.1-m8g.metal-24xl 79.14% <ø> (?)
6.1-m8g.metal-48xl 79.14% <ø> (?)

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.

@bchalios bchalios enabled auto-merge (rebase) July 29, 2025 11:38
@bchalios bchalios merged commit 1dac3b6 into firecracker-microvm:main Jul 29, 2025
8 checks passed
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