Move some stable test scripts to standard PR checkers. #16040
Conversation
This file contains 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
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no suggestions.
8 tasks
yutongzhang-microsoft
changed the title
xwjiang-ms
approved these changes
Dec 12, 2024
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.
Description of PR
In PR #15907, we initially added several test scripts to the onboarding PR checkers. After monitoring their performance over a few days, some of these scripts have proven to be stable. In this PR, we promote these stable scripts from the onboarding PR checkers to the standard PR checkers.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
In PR #15907, we initially added several test scripts to the onboarding PR checkers. After monitoring their performance over a few days, some of these scripts have proven to be stable. In this PR, we promote these stable scripts from the onboarding PR checkers to the standard PR checkers.
How did you do it?
In this PR, we promote these stable scripts from the onboarding PR checkers to the standard PR checkers.
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation