Minor fixes to unittest and future internal oovpa signatures conflict #223
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
…tInline_0__LTCG_ebx1_edx2_eax3
github-actions
bot
added
OOVPA
Member
Author
|
Low risk merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
One commit is forgotten to add to the #221 pull request with the unittest's symbol renamed.
The other commit is mainly to keep OOVPA signatures local only to OOVPA's group files. I am not entirely sure how this was missed duration of untangling from the manual scan process needs to access the OOVPA signatures directly. Relative to #218 pull request.