Skip to content

deps: specify explicit dependency features - #6175

Open
ShadowCurse wants to merge 1 commit into
firecracker-microvm:mainfrom
ShadowCurse:explicit_dep_features
Open

deps: specify explicit dependency features#6175
ShadowCurse wants to merge 1 commit into
firecracker-microvm:mainfrom
ShadowCurse:explicit_dep_features

Conversation

@ShadowCurse

Copy link
Copy Markdown
Contributor

Changes

Go over all dependencies we have and explicitly select only features we actually need. This reduces the number of transitive dependencies we pull and makes it harder to accidentally introduce new ones.

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.

@ShadowCurse ShadowCurse self-assigned this Sep 1, 2026
@codecov

codecov Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codecov Report

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

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6175      +/-   ##
==========================================
+ Coverage   83.01%   83.03%   +0.01%     
==========================================
  Files         277      277              
  Lines       30933    30928       -5     
==========================================
  Hits        25680    25680              
+ Misses       5253     5248       -5     
Flag Coverage Δ
5.10-m5n.metal 83.29% <ø> (+<0.01%) ⬆️
5.10-m6a.metal 82.66% <ø> (+0.01%) ⬆️
5.10-m6g.metal 80.13% <ø> (+0.01%) ⬆️
5.10-m6i.metal 83.29% <ø> (+0.01%) ⬆️
5.10-m7a.metal-48xl 82.65% <ø> (+0.01%) ⬆️
5.10-m7g.metal 80.13% <ø> (+0.01%) ⬆️
5.10-m7i.metal-24xl 83.27% <ø> (+0.01%) ⬆️
5.10-m7i.metal-48xl 83.27% <ø> (+0.01%) ⬆️
5.10-m8g.metal-24xl 80.13% <ø> (+0.01%) ⬆️
5.10-m8g.metal-48xl 80.13% <ø> (+0.01%) ⬆️
5.10-m8i.metal-48xl 83.27% <ø> (+0.01%) ⬆️
5.10-m8i.metal-96xl 83.27% <ø> (+0.01%) ⬆️
5.10-m9g.metal-48xl 80.13% <ø> (+0.01%) ⬆️
6.1-m5n.metal 83.32% <ø> (+0.01%) ⬆️
6.1-m6a.metal 82.69% <ø> (+0.01%) ⬆️
6.1-m6g.metal 80.13% <ø> (+0.01%) ⬆️
6.1-m6i.metal 83.32% <ø> (+0.01%) ⬆️
6.1-m7a.metal-48xl 82.68% <ø> (+0.01%) ⬆️
6.1-m7g.metal 80.13% <ø> (+0.01%) ⬆️
6.1-m7i.metal-24xl 83.33% <ø> (+<0.01%) ⬆️
6.1-m7i.metal-48xl 83.34% <ø> (+0.01%) ⬆️
6.1-m8g.metal-24xl 80.13% <ø> (+0.01%) ⬆️
6.1-m8g.metal-48xl 80.13% <ø> (+0.01%) ⬆️
6.1-m8i.metal-48xl 83.34% <ø> (+0.01%) ⬆️
6.1-m8i.metal-96xl 83.34% <ø> (+0.01%) ⬆️
6.1-m9g.metal-48xl 80.13% <ø> (+0.01%) ⬆️
6.18-m5n.metal 83.32% <ø> (+<0.01%) ⬆️
6.18-m6a.metal 82.68% <ø> (+0.01%) ⬆️
6.18-m6g.metal 80.15% <ø> (+0.01%) ⬆️
6.18-m6i.metal 83.32% <ø> (+0.01%) ⬆️
6.18-m7a.metal-48xl 82.68% <ø> (+0.01%) ⬆️
6.18-m7g.metal 80.15% <ø> (+0.01%) ⬆️
6.18-m7i.metal-24xl 83.34% <ø> (+0.01%) ⬆️
6.18-m7i.metal-48xl 83.34% <ø> (+0.01%) ⬆️
6.18-m8g.metal-24xl 80.15% <ø> (+0.01%) ⬆️
6.18-m8g.metal-48xl 80.15% <ø> (+0.01%) ⬆️
6.18-m8i.metal-48xl 83.34% <ø> (+0.01%) ⬆️
6.18-m8i.metal-96xl 83.33% <ø> (+0.01%) ⬆️
6.18-m9g.metal-48xl 80.15% <ø> (+0.01%) ⬆️

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

☔ View full report in Codecov by Harness.
📢 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.

Go over all dependencies we have and explicitly select only features we
actually need. This reduces the number of transitive dependencies we
pull and makes it harder to accidentally introduce new ones.

Signed-off-by: Egor Lazarchuk <yegorlz@amazon.co.uk>
@ShadowCurse
ShadowCurse force-pushed the explicit_dep_features branch from bfd39b7 to e189a3b Compare September 2, 2026 15:03
@ShadowCurse
ShadowCurse marked this pull request as ready for review September 2, 2026 15:42
@ShadowCurse ShadowCurse added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Sep 2, 2026

@zulinx86 zulinx86 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should consider documenting the policy for adding new dependencies in the developer guide. Otherwise, we may need to revisit the same issue periodically in the future. Maybe worth discussing between maintainers.

assert len(lines) == len(expected_output)
for line_number, line in enumerate(stderr.splitlines()):
# Need to strip off timestamps
print(line)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a print you used for debugging and forgot to remove, or is it intentional?

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.

2 participants