Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Downgrade #![deny(...)] to #![warn(...)] #4244

Merged
merged 1 commit into from
Nov 16, 2023

Conversation

roypat
Copy link
Contributor

@roypat roypat commented Nov 16, 2023

In our CI, we explicitly check that no warnings are present (by meanings of -Dwarnings during build tests). This means that there is no need to have #![deny(...)] instead of #![warn(...)] directives in the source code. On the other hand, having deny directives makes prototyping more annoying, as scrappy code will not compile until all compiler warnings are fixed (which might not neccessarily make sense when prototyping).

See also #4106

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

  • If a specific issue led to this PR, this PR closes the issue.
  • The description of changes is clear and encompassing.
  • Any required documentation changes (code and docs) are included in this PR.
  • API changes follow the Runbook for Firecracker API changes.
  • User-facing changes are mentioned in CHANGELOG.md.
  • All added/changed functionality is tested.
  • New TODOs link to an issue.
  • Commits meet contribution quality standards.

  • This functionality cannot be added in rust-vmm.

Copy link

codecov bot commented Nov 16, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a660fdf) 81.71% compared to head (a8b4f7d) 81.71%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4244   +/-   ##
=======================================
  Coverage   81.71%   81.71%           
=======================================
  Files         240      240           
  Lines       29239    29239           
=======================================
  Hits        23893    23893           
  Misses       5346     5346           
Flag Coverage Δ
4.14-c7g.metal 77.16% <ø> (ø)
4.14-m5d.metal 79.05% <ø> (-0.02%) ⬇️
4.14-m6a.metal 78.17% <ø> (ø)
4.14-m6g.metal 77.16% <ø> (ø)
4.14-m6i.metal 79.04% <ø> (ø)
5.10-c7g.metal 80.04% <ø> (ø)
5.10-m5d.metal 81.71% <ø> (-0.02%) ⬇️
5.10-m6a.metal 80.92% <ø> (ø)
5.10-m6g.metal 80.04% <ø> (ø)
5.10-m6i.metal 81.69% <ø> (ø)
6.1-c7g.metal 80.04% <ø> (ø)
6.1-m5d.metal 81.71% <ø> (ø)
6.1-m6a.metal 80.92% <ø> (ø)
6.1-m6g.metal 80.04% <ø> (ø)
6.1-m6i.metal 81.69% <ø> (ø)

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.

@roypat roypat added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Nov 16, 2023
In our CI, we explicitly check that no warnings are present (by meanings
of -Dwarnings during build tests). This means that there is no need to
have #![deny(...)] instead of #![warn(...)] directives in the source
code. On the other hand, having deny directives makes prototyping more
annoying, as scrappy code will not compile until all compiler warnings
are fixed (which might not neccessarily make sense when prototyping).

See also firecracker-microvm#4106

Signed-off-by: Patrick Roy <[email protected]>
@JonathanWoollett-Light
Copy link
Contributor

Opened rust-lang/rust-clippy#11822

@roypat roypat merged commit 5dec5e8 into firecracker-microvm:main Nov 16, 2023
5 checks passed
@roypat roypat deleted the no-deny branch April 15, 2024 14: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