Update impact area testing #21600
Open
Update impact area testing #21600
+579
−109
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
opcoder0
requested review from
bingwang-ms,
wangxin and
yxieca
as code owners
Collaborator
|
/azp run |
github-actions
bot
requested review from
BYGX-wcr,
bachalla,
cyw233,
r12f,
stepanblyschak,
xwjiang-ms and
yutongzhang-microsoft
|
Azure Pipelines failed to run 1 pipeline(s). |
opcoder0
force-pushed
the
feat/update-impact-area-test
branch
from
c7a0bee to
7fe44e8
Compare
Collaborator
|
/azp run |
|
Azure Pipelines failed to run 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: opcoder0 <[email protected]>
Signed-off-by: opcoder0 <[email protected]>
opcoder0
force-pushed
the
feat/update-impact-area-test
branch
from
674ee6f to
d6b4ea2
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of PR
The PR contains
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
To evaluate a more fine-grained impact based on the exact changes.
How did you do it?
See description above
How did you verify/test it?
Locally through unit testing.
Any platform specific information?
NA
Supported testbed topology if it's a new test case?
NA
Documentation
TBD