Skip to content

Enable tracing mode for release.sh and fix release.sh #5200

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

Conversation

zulinx86
Copy link
Contributor

@zulinx86 zulinx86 commented May 7, 2025

Changes

  • Enable tracing mode (set -x) for the future debugability
  • Fix release.sh by using upper case custom CPU template file names

Reason

The release script failed.
This will be forward-ported to the main branch after the release.

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 added 2 commits May 7, 2025 10:08
`set -x` shows what commands ran, which helps us identify what failed
in the release process.

Signed-off-by: Takahiro Itazuri <itazur@amazon.com>
I renamed the custom CPU template files uppercase, but I forgot to
update their names in release.sh.

Fixes: 2862941 ("chore: Use uppercase for custom CPU templates")
Signed-off-by: Takahiro Itazuri <itazur@amazon.com>
@zulinx86 zulinx86 added Status: Awaiting author Indicates that an issue or pull request requires author action Status: Awaiting review Indicates that a pull request is ready to be reviewed and removed Status: Awaiting author Indicates that an issue or pull request requires author action labels May 7, 2025
Copy link

codecov bot commented May 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.09%. Comparing base (3330cb8) to head (0406439).
Report is 2 commits behind head on firecracker-v1.12.

Additional details and impacted files
@@                Coverage Diff                 @@
##           firecracker-v1.12    #5200   +/-   ##
==================================================
  Coverage              83.09%   83.09%           
==================================================
  Files                    250      250           
  Lines                  26892    26892           
==================================================
  Hits                   22346    22346           
  Misses                  4546     4546           
Flag Coverage Δ
5.10-c5n.metal 83.59% <ø> (ø)
5.10-m5n.metal 83.57% <ø> (-0.02%) ⬇️
5.10-m6a.metal 82.81% <ø> (-0.01%) ⬇️
5.10-m6g.metal 79.38% <ø> (ø)
5.10-m6i.metal 83.57% <ø> (-0.01%) ⬇️
5.10-m7a.metal-48xl 82.80% <ø> (ø)
5.10-m7g.metal 79.38% <ø> (ø)
5.10-m7i.metal-24xl 83.55% <ø> (+<0.01%) ⬆️
5.10-m7i.metal-48xl 83.54% <ø> (-0.02%) ⬇️
5.10-m8g.metal-24xl 79.37% <ø> (ø)
5.10-m8g.metal-48xl 79.37% <ø> (ø)
6.1-c5n.metal 83.63% <ø> (+<0.01%) ⬆️
6.1-m5n.metal 83.62% <ø> (-0.01%) ⬇️
6.1-m6a.metal 82.85% <ø> (-0.01%) ⬇️
6.1-m6g.metal 79.38% <ø> (ø)
6.1-m6i.metal 83.62% <ø> (-0.02%) ⬇️
6.1-m7a.metal-48xl 82.84% <ø> (ø)
6.1-m7g.metal 79.38% <ø> (ø)
6.1-m7i.metal-24xl 83.64% <ø> (+<0.01%) ⬆️
6.1-m7i.metal-48xl 83.64% <ø> (-0.02%) ⬇️
6.1-m8g.metal-24xl 79.37% <ø> (ø)
6.1-m8g.metal-48xl 79.37% <ø> (ø)

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.

@zulinx86 zulinx86 enabled auto-merge (rebase) May 7, 2025 10:23
@zulinx86 zulinx86 merged commit 15e7490 into firecracker-microvm:firecracker-v1.12 May 7, 2025
8 of 9 checks passed
@zulinx86 zulinx86 deleted the firecracker-v1.12 branch May 8, 2025 07:42
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