Skip to content

fix: use the right base branch to detect changed files #4441

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 1 commit into from
Mar 15, 2024
Merged

fix: use the right base branch to detect changed files #4441

merged 1 commit into from
Mar 15, 2024

Conversation

wearyzen
Copy link
Contributor

@wearyzen wearyzen commented Feb 9, 2024

Changes:

Use either $BUILDKITE_PULL_REQUEST_BASE_BRANCH if available
instead of main to get list of changed files.

Reason:

Comparing changed files with main leads to running unnecessary tests like buid_devctr even when there is no Dockerfile change in the release branch.

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 Feb 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.53%. Comparing base (094f066) to head (93488b2).

Additional details and impacted files
@@                 Coverage Diff                  @@
##           firecracker-v1.6    #4441      +/-   ##
====================================================
- Coverage             81.55%   81.53%   -0.03%     
====================================================
  Files                   240      240              
  Lines                 29367    29367              
====================================================
- Hits                  23951    23945       -6     
- Misses                 5416     5422       +6     
Flag Coverage Δ
4.14-c7g.metal 76.96% <ø> (ø)
4.14-m5d.metal 78.85% <ø> (-0.03%) ⬇️
4.14-m6a.metal 77.97% <ø> (ø)
4.14-m6g.metal 76.96% <ø> (ø)
4.14-m6i.metal 78.84% <ø> (ø)
5.10-c7g.metal 79.85% <ø> (ø)
5.10-m5d.metal 81.51% <ø> (-0.03%) ⬇️
5.10-m6a.metal 80.73% <ø> (ø)
5.10-m6g.metal 79.85% <ø> (ø)
5.10-m6i.metal 81.51% <ø> (ø)
6.1-c7g.metal 79.85% <ø> (ø)
6.1-m5d.metal 81.51% <ø> (-0.03%) ⬇️
6.1-m6a.metal 80.73% <ø> (ø)
6.1-m6g.metal 79.85% <ø> (ø)
6.1-m6i.metal 81.51% <ø> (ø)

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.

Changes:
Use either $BUILDKITE_PULL_REQUEST_BASE_BRANCH if available
instead of main to get list of changed files.

Reason:
Comparing changed files with main leads to running
unnecessary tests like buid_devctr even when there is no
Dockerfile change in the release branch.

Signed-off-by: Sudan Landge <[email protected]>
@wearyzen wearyzen marked this pull request as ready for review March 15, 2024 13:02
@wearyzen wearyzen self-assigned this Mar 15, 2024
@wearyzen wearyzen requested review from pb8o and roypat March 15, 2024 13:03
@wearyzen wearyzen added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Mar 15, 2024
@wearyzen wearyzen changed the title Jailer doc 1 6 fix: use the right base branch to detect changed files Mar 15, 2024
@wearyzen wearyzen merged commit 96e24a0 into firecracker-microvm:firecracker-v1.6 Mar 15, 2024
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