Skip to content

fix(ci): Dont run functional tests if changing patch series #5339

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

roypat
Copy link
Contributor

@roypat roypat commented Jul 31, 2025

Currently, we often get stuck with the problem where something in the host kernel breaks that causes functional tests to fail, but we cannot update the patch series from which the host kernel gets built, because functional tests are failing. Break this cyclic dependency by simply not running functional tests when updating only the patch series (as they dont test the updated kernel anyway.

Changes

...

Reason

...

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.

@roypat roypat force-pushed the sh-break-cyclic-deps branch from bebd7c1 to f10b046 Compare July 31, 2025 13:18
@roypat roypat force-pushed the sh-break-cyclic-deps branch from f10b046 to de34cee Compare July 31, 2025 13:22
kalyazin
kalyazin previously approved these changes Jul 31, 2025
Copy link

codecov bot commented Jul 31, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.90%. Comparing base (ca6a13b) to head (74d96e9).
⚠️ Report is 1 commits behind head on feature/secret-hiding.

Additional details and impacted files
@@                    Coverage Diff                    @@
##           feature/secret-hiding    #5339      +/-   ##
=========================================================
- Coverage                  81.94%   81.90%   -0.04%     
=========================================================
  Files                        250      250              
  Lines                      27612    27612              
=========================================================
- Hits                       22626    22615      -11     
- Misses                      4986     4997      +11     
Flag Coverage Δ
5.10-c5n.metal 82.09% <ø> (ø)
5.10-m5n.metal 82.09% <ø> (ø)
5.10-m6a.metal 81.26% <ø> (+<0.01%) ⬆️
5.10-m6g.metal 77.91% <ø> (ø)
5.10-m6i.metal 82.07% <ø> (-0.01%) ⬇️
5.10-m7a.metal-48xl 81.23% <ø> (ø)
5.10-m7g.metal 77.91% <ø> (ø)
5.10-m7i.metal-24xl 82.04% <ø> (ø)
5.10-m7i.metal-48xl 82.04% <ø> (-0.01%) ⬇️
5.10-m8g.metal-24xl 77.91% <ø> (ø)
5.10-m8g.metal-48xl 77.91% <ø> (ø)
6.1-c5n.metal 82.12% <ø> (-0.01%) ⬇️
6.1-m5n.metal 82.13% <ø> (-0.05%) ⬇️
6.1-m6a.metal 81.29% <ø> (-0.01%) ⬇️
6.1-m6g.metal 77.91% <ø> (ø)
6.1-m6i.metal 82.13% <ø> (ø)
6.1-m7a.metal-48xl 81.29% <ø> (+<0.01%) ⬆️
6.1-m7g.metal 77.91% <ø> (ø)
6.1-m7i.metal-24xl 82.14% <ø> (ø)
6.1-m7i.metal-48xl 82.14% <ø> (+<0.01%) ⬆️
6.1-m8g.metal-24xl 77.91% <ø> (ø)
6.1-m8g.metal-48xl 77.91% <ø> (-0.01%) ⬇️
6.16-c5n.metal 82.16% <ø> (-0.01%) ⬇️
6.16-m5n.metal 82.16% <ø> (ø)
6.16-m6a.metal 81.34% <ø> (ø)
6.16-m6g.metal 77.95% <ø> (-0.01%) ⬇️
6.16-m6i.metal 82.16% <ø> (ø)
6.16-m7a.metal-48xl 81.32% <ø> (ø)
6.16-m7g.metal 77.95% <ø> (ø)
6.16-m7i.metal-24xl 82.18% <ø> (ø)
6.16-m7i.metal-48xl 82.18% <ø> (-0.01%) ⬇️
6.16-m8g.metal-24xl 77.95% <ø> (ø)
6.16-m8g.metal-48xl 77.95% <ø> (ø)

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.

Currently, we often get stuck with the problem where something in the
host kernel breaks that causes functional tests to fail, but we cannot
update the patch series from which the host kernel gets built, because
functional tests are failing. Break this cyclic dependency by simply not
running functional tests when updating only the patch series (as they
dont test the updated kernel anyway.

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

roypat commented Jul 31, 2025

merging with this without CI passing because we're exactly in the situation this PR is fixing: CI is failing because host kernel broken

@roypat roypat merged commit c09ce81 into firecracker-microvm:feature/secret-hiding Jul 31, 2025
5 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants