[202511][cherry][hft]: Fix conditional mark in high frequency telemetry test (#21482)#23008
Merged
vmittal-msft merged 1 commit intosonic-net:202511from Mar 17, 2026
Conversation
…et#21482) What is the motivation for this PR? Wrong condition for skipping HFT test How did you do it? Correct it as described in this comment: sonic-net#20379 (comment) Signed-off-by: Ze Gan <[email protected]> Signed-off-by: Priyansh Tratiya <[email protected]>
PriyanshTratiya
requested review from
BYGX-wcr and
yutongzhang-microsoft
as code owners
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
PriyanshTratiya
requested review from
Pterosaur and
vmittal-msft
and removed request for
xwjiang-ms
vmittal-msft
approved these changes
Mar 16, 2026
vmittal-msft
approved these changes
Mar 17, 2026
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.
Manual Cherry Pick, includes both:
What is the motivation for this PR?
Wrong condition for skipping HFT test
How did you do it?
Correct it as described in this comment: #20379 (comment)
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
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