Skip to content

Conversation

Manciukic
Copy link
Contributor

@Manciukic Manciukic commented Jul 18, 2025

Changes

Fix the block tests by using the correct fixture name.

Reason

PCI pipeline is failing :(

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.

Fix the block tests by using the correct fixture name.

Fixes: eb7248f ("refactor(test): add uvm_plain_acpi and _6_1 fixtures")
Signed-off-by: Riccardo Mancini <[email protected]>
@Manciukic Manciukic marked this pull request as ready for review July 18, 2025 09:19
@Manciukic Manciukic added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Jul 18, 2025
@Manciukic Manciukic changed the title fix(test_block): correct fixture name s/uvm_any_acpi/uvm_plain_acpi/ [feature/pcie] fix(test_block): correct fixture name s/uvm_any_acpi/uvm_plain_acpi/ Jul 18, 2025
Copy link

codecov bot commented Jul 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.16%. Comparing base (ba962ba) to head (d5305af).
Report is 1 commits behind head on feature/pcie.

Additional details and impacted files
@@              Coverage Diff              @@
##           feature/pcie    #5313   +/-   ##
=============================================
  Coverage         80.16%   80.16%           
=============================================
  Files               265      265           
  Lines             30863    30863           
=============================================
  Hits              24741    24741           
  Misses             6122     6122           
Flag Coverage Δ
5.10-c5n.metal 79.90% <ø> (ø)
5.10-m5n.metal 79.90% <ø> (-0.01%) ⬇️
5.10-m6a.metal 79.10% <ø> (+<0.01%) ⬆️
5.10-m6g.metal 76.49% <ø> (ø)
5.10-m6i.metal 79.89% <ø> (ø)
5.10-m7a.metal-48xl 79.08% <ø> (ø)
5.10-m7g.metal 76.49% <ø> (ø)
5.10-m7i.metal-24xl 79.87% <ø> (+<0.01%) ⬆️
5.10-m7i.metal-48xl 79.87% <ø> (+<0.01%) ⬆️
5.10-m8g.metal-24xl 76.49% <ø> (ø)
5.10-m8g.metal-48xl 76.49% <ø> (-0.01%) ⬇️
6.1-c5n.metal 79.94% <ø> (-0.01%) ⬇️
6.1-m5n.metal 79.94% <ø> (ø)
6.1-m6a.metal 79.14% <ø> (ø)
6.1-m6g.metal 76.49% <ø> (ø)
6.1-m6i.metal 79.94% <ø> (-0.01%) ⬇️
6.1-m7a.metal-48xl 79.13% <ø> (-0.01%) ⬇️
6.1-m7g.metal 76.49% <ø> (ø)
6.1-m7i.metal-24xl 79.95% <ø> (+<0.01%) ⬆️
6.1-m7i.metal-48xl 79.96% <ø> (+<0.01%) ⬆️
6.1-m8g.metal-24xl 76.49% <ø> (ø)
6.1-m8g.metal-48xl 76.49% <ø> (ø)

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.

@Manciukic Manciukic requested a review from ShadowCurse July 18, 2025 11:32
@Manciukic Manciukic merged commit 49a0cff into firecracker-microvm:feature/pcie Jul 21, 2025
8 checks passed
@Manciukic Manciukic deleted the pcie/fix-block-test branch July 21, 2025 12:27
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