Skip to content

test: Support pre-release version #5229

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

Merged
merged 3 commits into from
Jun 9, 2025
Merged

Conversation

zulinx86
Copy link
Contributor

@zulinx86 zulinx86 commented May 28, 2025

Changes

Use "semver" library instead of "packaging".

Reason

The "packaging" library only allows a limited set of pre-release names 1, while the semantic versioning permits any alphanumeric charcters 2.

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 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.

@zulinx86 zulinx86 added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label May 28, 2025
@zulinx86 zulinx86 enabled auto-merge (rebase) May 28, 2025 16:24
Copy link

codecov bot commented May 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.90%. Comparing base (a93e9f2) to head (81ab3ba).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5229      +/-   ##
==========================================
+ Coverage   82.84%   82.90%   +0.05%     
==========================================
  Files         250      250              
  Lines       26967    26967              
==========================================
+ Hits        22342    22356      +14     
+ Misses       4625     4611      -14     
Flag Coverage Δ
5.10-c5n.metal 83.33% <ø> (ø)
5.10-m5n.metal 83.33% <ø> (-0.01%) ⬇️
5.10-m6a.metal 82.55% <ø> (+<0.01%) ⬆️
5.10-m6g.metal 79.16% <ø> (ø)
5.10-m6i.metal 83.32% <ø> (-0.01%) ⬇️
5.10-m7a.metal-48xl 82.53% <ø> (?)
5.10-m7g.metal 79.16% <ø> (ø)
5.10-m7i.metal-24xl 83.29% <ø> (?)
5.10-m7i.metal-48xl 83.28% <ø> (?)
5.10-m8g.metal-24xl 79.16% <ø> (?)
5.10-m8g.metal-48xl 79.16% <ø> (?)
6.1-c5n.metal 83.38% <ø> (ø)
6.1-m5n.metal 83.38% <ø> (ø)
6.1-m6a.metal 82.59% <ø> (ø)
6.1-m6g.metal 79.16% <ø> (ø)
6.1-m6i.metal 83.37% <ø> (ø)
6.1-m7a.metal-48xl 82.59% <ø> (?)
6.1-m7g.metal 79.16% <ø> (ø)
6.1-m7i.metal-24xl 83.39% <ø> (?)
6.1-m7i.metal-48xl 83.38% <ø> (?)
6.1-m8g.metal-24xl 79.16% <ø> (?)
6.1-m8g.metal-48xl 79.16% <ø> (?)

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.

pb8o
pb8o previously approved these changes May 30, 2025
Copy link
Contributor

@pb8o pb8o left a comment

Choose a reason for hiding this comment

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

LGTM. No changes are needed in release.sh?

@zulinx86
Copy link
Contributor Author

LGTM. No changes are needed in release.sh?

without any changes, it worked!

The "packaging" library only allows a limited set of pre-release names
[1], while the semantic versioning permits any alphanumeric charcters
[2]. Use "semver" library instead.

[1]: https://github.com/pypa/packaging/blob/7952e97c650cd70962a45018e11b760d7b1e1325/src/packaging/version.py#L122-L127
[2]: https://semver.org/#backusnaur-form-grammar-for-valid-semver-versions

Signed-off-by: Takahiro Itazuri <[email protected]>
@roypat
Copy link
Contributor

roypat commented Jun 5, 2025

(had to rebuild the docker container cuz I accidentally overwrote it when doing the toolchain update on tuesday)

@zulinx86 zulinx86 merged commit e36e774 into firecracker-microvm:main Jun 9, 2025
6 of 7 checks passed
@zulinx86 zulinx86 deleted the semver branch June 10, 2025 00:13
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