[dhcp_relay] ignore mem checker with stress test #21598
Open
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
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Blueve
approved these changes
Dec 8, 2025
Xichen96
added
Request for 202505 branch
Request for 202511 branch
Signed-off-by: Xichen Lin <[email protected]>
Xichen96
force-pushed
the
dev/xichenlin/dhcp-ignore-mem-check
branch
from
befeef2 to
800c0ba
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
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
During the dhcp counter stress test, mem checker might gave an alarm that mem is smaller than threshold. It's stress test so its expected.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Test produce mem checker failure and we dont want that.
How did you do it?
Add ignore loganalyzer
How did you verify/test it?
Run test, and passed
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation