Skip to content
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

[Rebase & FF] [Cherry-pick] Get all the missing commits from 202302 into 202311 #428

Merged

Conversation

kenlautner
Copy link
Contributor

@kenlautner kenlautner commented Feb 2, 2024

Description

Cherry-pick the commits from 202302 that are missing from 202311 since the creation of the release branch.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

How This Was Tested

CI

Integration Instructions

N/A

uefibot and others added 7 commits January 29, 2024 13:10
synced local file(s) with
[microsoft/mu_devops](https://github.com/microsoft/mu_devops).

🤖: View the [Repo File Sync Configuration
File](https://github.com/microsoft/mu_devops/blob/main/.sync/Files.yml)
to see how files are synced.

---

This PR was created automatically by the
[repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action)
workflow run
[#7581631119](https://github.com/microsoft/mu_devops/actions/runs/7581631119)

Signed-off-by: Project Mu UEFI Bot <[email protected]>
C code changes for building the code as 64-bit.

Signed-off-by: Michael Kubacki <[email protected]>
Allows the module to be built for 64-bit SEC.

Signed-off-by: Michael Kubacki <[email protected]>
Bumps [actions/cache](https://github.com/actions/cache) from 3 to 4.

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
## Description

Updates edk2-pytool-extensions and edk2-pytool-library to work with the
latest commit of MU_BASECORE

For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_

- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
    flow, or firmware?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
    in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
    a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
  - **Tests** - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
    outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
    on an a separate Web page, ...

## How This Was Tested

N/A

## Integration Instructions

N/A
Bumps
[robinraju/release-downloader](https://github.com/robinraju/release-downloader)
from 1.8 to 1.9.

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@kenlautner kenlautner added the impact:non-functional Does not have a functional impact label Feb 2, 2024
@codecov-commenter
Copy link

codecov-commenter commented Feb 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (d567b5e) 12.13% compared to head (fdaf524) 12.13%.

Additional details and impacted files
@@               Coverage Diff               @@
##           release/202311     #428   +/-   ##
===============================================
  Coverage           12.13%   12.13%           
===============================================
  Files                 110      110           
  Lines               19022    19022           
  Branches             1363     1363           
===============================================
  Hits                 2308     2308           
  Misses              16697    16697           
  Partials               17       17           
Flag Coverage Δ
HidPkg 2.80% <ø> (ø)
MfciPkg 38.25% <ø> (ø)
MsCorePkg 1.43% <ø> (ø)
MsWheaPkg 7.17% <ø> (ø)
XmlSupportPkg 25.41% <ø> (ø)

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.

@kenlautner kenlautner changed the title [Cherry-pick] Get all the missing commits from 202302 into 202311 [Rebase & FF] [Cherry-pick] Get all the missing commits from 202302 into 202311 Feb 2, 2024
@makubacki makubacki merged commit 1b10bac into release/202311 Feb 2, 2024
30 of 33 checks passed
@makubacki makubacki deleted the personal/klautner/cherry_pick_missing_commits branch February 2, 2024 21:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:non-functional Does not have a functional impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants