Closed TaylorBeebe closed 1 month ago
@apop5 @makubacki @os-d
@TaylorBeebe, ha, thanks for catching this. I will fix it.
@os-d
No problem π
If you want this test to pass, I think the first step is to look into removing the following lines:
If I remember correctly, one of the issues with removing the above lines is detailed in our Teams chat toward when you joined the team. The project led by Aaron hits a different issue if the above lines are removed which I think he remembers.
I'm pretty limited in what support I can provide, but feel free to reach out if questions arise.
Is there an existing issue for this?
Current Behavior
PR 528 updated the MemoryOutsideEfiMemoryMapIsInaccessible() test to check the return status of ValidateRegionAttributes(). ValidateRegionAttributes() returns a boolean, not a status. So, interpreting the FALSE return value is being mistaken for an EFI_SUCCESS return value.
I know, I know... usually we return a status... SOMETIMES I COLORED OUTSIDE THE LINES π
Expected Behavior
The AllowUnmappedRegions argument of ValidateRegionAttributes() dictates if EFI_NO_MAPPING is acceptable for the region. So, the MemoryOutsideEfiMemoryMapIsInaccessible() test was already checking for EFI_NO_MAPPING but now the test will only pass if the required conditions are not met.
Steps To Reproduce
N/A
Build Environment
Version Information
Urgency
Low
Are you going to fix this?
Someone else needs to fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
Miss y'all β€οΈ Hope everything is going well π