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

Repo File Sync: Update to Mu DevOps 9.1.2 #192

Merged
merged 1 commit into from
Feb 6, 2024

Conversation

uefibot
Copy link
Collaborator

@uefibot uefibot commented Feb 6, 2024

synced local file(s) with microsoft/mu_devops.

🤖: View the Repo File Sync Configuration File to see how files are synced.


This PR was created automatically by the repo-file-sync-action workflow run #7792517170

@uefibot uefibot added the type:file-sync Files automatically synced from another repo label Feb 6, 2024
@makubacki makubacki changed the title Repo File Sync: synced file(s) with microsoft/mu_devops Repo File Sync: Update to Mu DevOps 9.1.2 Feb 6, 2024
@ProjectMuBot ProjectMuBot merged commit cd8791d into master Feb 6, 2024
8 checks passed
@ProjectMuBot ProjectMuBot deleted the repo-sync/mu_devops/default branch February 6, 2024 01:09
julorenz117 pushed a commit to julorenz117/mu that referenced this pull request Aug 19, 2024
## Description

This test used to reside in MdePkg, but because an AARCH64
implementation needed to be added to the test which necessitated a
dependency on ArmPkg, the test needed to be removed from MdePkg to
adhere to our rule of no dependencies from MU_BASECORE to other repos.
This PR adds the test app with the added AARCH64 implementation and
rewrites the X64 page split test to remove the need for structs
representing each page table level.

- [ ] 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, ...
- [x] 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

Running on Q35 and SBSA

## Integration Instructions

N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:file-sync Files automatically synced from another repo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants