[Impacted Area Based PR testing] Roll out t1-lag PR checker.#16403
Merged
wangxin merged 2 commits intosonic-net:masterfrom Jan 10, 2025
Merged
[Impacted Area Based PR testing] Roll out t1-lag PR checker.#16403wangxin merged 2 commits intosonic-net:masterfrom
wangxin merged 2 commits intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
yutongzhang-microsoft
force-pushed
the
yutongzhang/roll_out_t1
branch
from
3851f01 to
c54c9d2
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wangxin
approved these changes
Jan 10, 2025
11 tasks
wangxin
pushed a commit
that referenced
this pull request
Jan 22, 2025
) What is the motivation for this PR? In PRs #15666 and #16403, we partially rolled out the T0 and T1 PR checkers, considering resource utilization since these checkers require over 20 instances and needed to run in parallel with the legacy PR checkers. After a period of observation, we have confirmed the stability of the new system. In this PR, we complete the rollout of the remaining T0 and T1 PR checkers and officially deprecate the old PR checkers. At the same time, we have added all test scripts into PR testing, and we will gather scripts though pytest mark, so we don't need onboarding PR checkers anymore. How did you do it? In this PR, we complete the rollout of the remaining T0 and T1 PR checkers and officially deprecate the old PR checkers. How did you verify/test it? Test by pipeline itself, to see if we can successfully pass the PR checkers.
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this pull request
Mar 15, 2025
…et#16403) In sonic-net#15666, we introduced a new approach to PR testing called Impacted Area-Based PR Testing. This model will be rolled out in phases. This PR represents step 2 of the rollout, specifically implementing the t1-lag PR checker partly.
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this pull request
Mar 15, 2025
…ic-net#16598) What is the motivation for this PR? In PRs sonic-net#15666 and sonic-net#16403, we partially rolled out the T0 and T1 PR checkers, considering resource utilization since these checkers require over 20 instances and needed to run in parallel with the legacy PR checkers. After a period of observation, we have confirmed the stability of the new system. In this PR, we complete the rollout of the remaining T0 and T1 PR checkers and officially deprecate the old PR checkers. At the same time, we have added all test scripts into PR testing, and we will gather scripts though pytest mark, so we don't need onboarding PR checkers anymore. How did you do it? In this PR, we complete the rollout of the remaining T0 and T1 PR checkers and officially deprecate the old PR checkers. How did you verify/test it? Test by pipeline itself, to see if we can successfully pass the PR checkers.
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
3 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
In #15666, we introduced a new approach to PR testing called
Impacted Area-Based PR Testing. This model will be rolled out in phases. This PR represents step 2 of the rollout, specifically implementing the t1-lag PR checker partly.Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
In #15666, we introduced a new approach to PR testing called
Impacted Area-Based PR Testing. This model will be rolled out in phases. This PR represents step 2 of the rollout, specifically implementing the t1-lag PR checker partly.How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation