feat: add cancel_pr for testplan.py#23101
Merged
StormLiangMS merged 1 commit intosonic-net:masterfrom Mar 19, 2026
Merged
Conversation
Signed-off-by: Austin Pham <austinpham@microsoft.com>
Collaborator
|
/azp run |
github-actions
bot
requested review from
wangxin,
xwjiang-ms and
yutongzhang-microsoft
12 tasks
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
hi @auspham could you follow the template to add details? |
auspham
added
Request for 202505 branch
Request for 202511 branch
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Mar 19, 2026
What is the motivation for this PR? Currently, when running a new testplan, there is no safety check to cancel all the previous dangling job. This add the ability to test_plan.py to cancel all related job with PR number using cancel_pr. However this PR does not add the call, only the implementation. The real call will be implemented in sonic-net#22861 How did you do it? Added a cancel_pr method that hits Elastictest endpoint API to cancel all previous job for the same PR How did you verify/test it? Verified locally and manually using CI Signed-off-by: Austin Pham <austinpham@microsoft.com> Signed-off-by: mssonicbld <sonicbld@microsoft.com>
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Mar 19, 2026
What is the motivation for this PR? Currently, when running a new testplan, there is no safety check to cancel all the previous dangling job. This add the ability to test_plan.py to cancel all related job with PR number using cancel_pr. However this PR does not add the call, only the implementation. The real call will be implemented in sonic-net#22861 How did you do it? Added a cancel_pr method that hits Elastictest endpoint API to cancel all previous job for the same PR How did you verify/test it? Verified locally and manually using CI Signed-off-by: Austin Pham <austinpham@microsoft.com> Signed-off-by: mssonicbld <sonicbld@microsoft.com>
Collaborator
|
Cherry-pick PR to 202511: #23116 |
Collaborator
|
Cherry-pick PR to 202505: #23117 |
This was referenced Mar 19, 2026
mssonicbld
pushed a commit
that referenced
this pull request
Mar 23, 2026
What is the motivation for this PR? Currently, when running a new testplan, there is no safety check to cancel all the previous dangling job. This add the ability to test_plan.py to cancel all related job with PR number using cancel_pr. However this PR does not add the call, only the implementation. The real call will be implemented in #22861 How did you do it? Added a cancel_pr method that hits Elastictest endpoint API to cancel all previous job for the same PR How did you verify/test it? Verified locally and manually using CI Signed-off-by: Austin Pham <austinpham@microsoft.com> Signed-off-by: mssonicbld <sonicbld@microsoft.com>
mssonicbld
added
Included in 202511 branch
and removed
Created PR to 202511 branch
labels
vrajeshe
pushed a commit
to vrajeshe/sonic-mgmt
that referenced
this pull request
Mar 23, 2026
What is the motivation for this PR? Currently, when running a new testplan, there is no safety check to cancel all the previous dangling job. This add the ability to test_plan.py to cancel all related job with PR number using cancel_pr. However this PR does not add the call, only the implementation. The real call will be implemented in sonic-net#22861 How did you do it? Added a cancel_pr method that hits Elastictest endpoint API to cancel all previous job for the same PR How did you verify/test it? Verified locally and manually using CI Signed-off-by: Austin Pham <austinpham@microsoft.com> Signed-off-by: Venkata Gouri Rajesh Etla <vrajeshe@cisco.com>
mssonicbld
added a commit
that referenced
this pull request
Mar 25, 2026
What is the motivation for this PR? Currently, when running a new testplan, there is no safety check to cancel all the previous dangling job. This add the ability to test_plan.py to cancel all related job with PR number using cancel_pr. However this PR does not add the call, only the implementation. The real call will be implemented in #22861 How did you do it? Added a cancel_pr method that hits Elastictest endpoint API to cancel all previous job for the same PR How did you verify/test it? Verified locally and manually using CI Signed-off-by: Austin Pham <austinpham@microsoft.com> Signed-off-by: mssonicbld <sonicbld@microsoft.com> Co-authored-by: Austin (Thang Pham) <austinpham@microsoft.com>
mssonicbld
added
Included in 202505 branch
and removed
Created PR to 202505 branch
labels
ravaliyel
pushed a commit
to ravaliyel/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
What is the motivation for this PR? Currently, when running a new testplan, there is no safety check to cancel all the previous dangling job. This add the ability to test_plan.py to cancel all related job with PR number using cancel_pr. However this PR does not add the call, only the implementation. The real call will be implemented in sonic-net#22861 How did you do it? Added a cancel_pr method that hits Elastictest endpoint API to cancel all previous job for the same PR How did you verify/test it? Verified locally and manually using CI Signed-off-by: Austin Pham <austinpham@microsoft.com>
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
4 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
Summary: Adding the ability to cancel previous PR to integrate with #22861
Fixes # (issue) 37065882
Type of change
Back port request
Approach
What is the motivation for this PR?
Currently, when running a new testplan, there is no safety check to cancel all the previous dangling job.
This add the ability to test_plan.py to cancel all related job with PR number using cancel_pr. However this PR does not add the call, only the implementation. The real call will be implemented in #22861
How did you do it?
Added a cancel_pr method that hits Elastictest endpoint API to cancel all previous job for the same PR
How did you verify/test it?
Verified locally and manually using CI
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation