[action] [PR:13066] [BGP Memory Leak] Add FRR memory checker in the continuous link flap test #14234
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
…test (sonic-net#13066) * Add bgp memory checker in the continuous link flap test
9 tasks
|
Original PR: #13066 |
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-mgmt |
|
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
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:
This is to cover the BGP memory leak test gap.
Previously we have an issue in FRR(FRRouting/frr#15459), which caused memory leak.
Type of change
Back port request
Approach
What is the motivation for this PR?
This is to cover the BGP memory leak test gap.
How did you do it?
I added a checker for the FRR daemons(bgpd and zebra) used memory in the test test_cont_link_flap.py. The reason why I added the checker in test_cont_link_flap.py but not the stress route test, is because we already have some memory and cpu checkers in the link flap test. And the link flap also causes routes announce/withdraw like what we have in the stress route test.
How did you verify/test it?
Run the test and it passed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation