Repository navigation
test: update bounded owner composition executable caps - #876
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A full bounded local Windows PowerShell source-control preflight reached its final owner-lifetime composition check and refused two maintained optimized fixture executables: 82,944 and 82,432 bytes exceed their old 80 KiB caps. This change raises only those two fixed executable caps to 84 KiB in the measurement and final gate. The guest DLL, default intermediate, witness DLL and 16 MiB total bounds remain unchanged.
One focused PS5 composition run passed both 14-case native paths and ten witness controls; the unchanged default intermediate remains outside its cap as expected. Independent source review passed. This is a preflight fixture correction; hosted VM and installed-owner acceptance remain pending.