Skip to content

Conversation

@roypat
Copy link
Contributor

@roypat roypat commented Jan 16, 2025

If cmd_test is instructed to build its own binaries (e.g. being ran
outside of CI), and the environment specifies that A/B-tests should
be ran, then we not only need to build the currently checked out commit
(the "B" revision), but also an "A" binary based on the value of the
BUILDKITE_PULL_REQUEST_BASE_BRANCH environment variable.

Signed-off-by: Patrick Roy [email protected]## 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 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.

@codecov
Copy link

codecov bot commented Jan 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.95%. Comparing base (94826a8) to head (7d654b9).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4998   +/-   ##
=======================================
  Coverage   83.95%   83.95%           
=======================================
  Files         248      248           
  Lines       27839    27839           
=======================================
  Hits        23371    23371           
  Misses       4468     4468           
Flag Coverage Δ
5.10-c5n.metal 84.53% <ø> (ø)
5.10-m5n.metal 84.51% <ø> (-0.01%) ⬇️
5.10-m6a.metal 83.79% <ø> (-0.01%) ⬇️
5.10-m6g.metal 80.63% <ø> (ø)
5.10-m6i.metal 84.50% <ø> (-0.01%) ⬇️
5.10-m7g.metal 80.63% <ø> (ø)
6.1-c5n.metal 84.53% <ø> (+<0.01%) ⬆️
6.1-m5n.metal 84.51% <ø> (ø)
6.1-m6a.metal 83.79% <ø> (-0.01%) ⬇️
6.1-m6g.metal 80.63% <ø> (ø)
6.1-m6i.metal 84.50% <ø> (ø)
6.1-m7g.metal 80.63% <ø> (ø)

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.

pb8o
pb8o previously approved these changes Jan 16, 2025
@roypat roypat added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Jan 16, 2025
If `cmd_test` is instructed to build its own binaries (e.g. being ran
outside of CI), and the environment specifies that A/B-tests should
be ran, then we not only need to build the currently checked out commit
(the "B" revision), but also an "A" binary based on the value of the
`BUILDKITE_PULL_REQUEST_BASE_BRANCH` environment variable.

Signed-off-by: Patrick Roy <[email protected]>
bchalios
bchalios previously approved these changes Jan 16, 2025
@roypat roypat requested a review from pb8o January 16, 2025 10:14
pb8o
pb8o previously approved these changes Jan 16, 2025
A quick blurb about which environment variables need to be set to run
things like test_vulnerabilities.py locally.

Signed-off-by: Patrick Roy <[email protected]>
@roypat roypat dismissed stale reviews from pb8o and bchalios via 7d654b9 January 16, 2025 11:22
@roypat roypat force-pushed the functional-ab-locally branch from 37a90da to 7d654b9 Compare January 16, 2025 11:22
@bchalios bchalios merged commit 9ac6f3a into firecracker-microvm:main Jan 16, 2025
6 of 7 checks passed
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.

4 participants