-
Notifications
You must be signed in to change notification settings - Fork 718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[test_tunnel_memory_leak] The memory leak check mechanism need to be updated #11403
Comments
echuawu
added a commit
to echuawu/sonic-mgmt
that referenced
this issue
Feb 7, 2024
Skip it by github issue sonic-net#11403 on dualtor-64 topology Change-Id: I767b31b8c62533fae216e9e8d67ddf8cd4bfca51
8 tasks
bingwang-ms
pushed a commit
that referenced
this issue
Feb 12, 2024
Skip it by github issue #11403 on dualtor-64 topology Change-Id: I767b31b8c62533fae216e9e8d67ddf8cd4bfca51
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this issue
Mar 22, 2024
Skip it by github issue sonic-net#11403 on dualtor-64 topology Change-Id: I767b31b8c62533fae216e9e8d67ddf8cd4bfca51
8 tasks
mssonicbld
pushed a commit
that referenced
this issue
Mar 22, 2024
Skip it by github issue #11403 on dualtor-64 topology Change-Id: I767b31b8c62533fae216e9e8d67ddf8cd4bfca51
echuawu
added a commit
to echuawu/sonic-mgmt
that referenced
this issue
Mar 22, 2024
Skip it by github issue sonic-net#11403 on dualtor-64 topology Change-Id: Iaba470f9f0c8dd0ac295d3a81118d443345bcbe5
This was referenced Mar 22, 2024
@yxieca are you aware of someone going to fix this issue? no assignee. |
@ZhaohuiS Can you please help take a look at this issue? |
@ZhaohuiS Kindly ping on this issue. |
Waiting for #13698 (review) merged, then will use this fixture |
bingwang-ms
pushed a commit
that referenced
this issue
Aug 20, 2024
Skip it by github issue #11403 on dualtor-64 topology Change-Id: Iaba470f9f0c8dd0ac295d3a81118d443345bcbe5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The test logic is flowed. The test tries to trigger tunnel packet handler and check the memory increase. However it checks swss docker using "docker state swss --no-stream". This considers the memory of swss docker + all processes. Since the while docker is considered there might be some temporal memory increased due to usage by docker subsystem as you can see in the running log.
Overall, the test needs to be more deterministic in figuring out the memory leak and not use very generic mechanism as used today.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Additional information you deem important:
The text was updated successfully, but these errors were encountered: