[202305] Update skip condition for test_tunnel_memory_leak (#12132)#12131
Merged
bingwang-ms merged 1 commit intosonic-net:202305from Aug 20, 2024
Merged
[202305] Update skip condition for test_tunnel_memory_leak (#12132)#12131bingwang-ms merged 1 commit intosonic-net:202305from
bingwang-ms merged 1 commit intosonic-net:202305from
Conversation
Skip it by github issue sonic-net#11403 on dualtor-64 topology Change-Id: Iaba470f9f0c8dd0ac295d3a81118d443345bcbe5
8 tasks
liat-grozovik
changed the title
liat-grozovik
changed the title
roy-sror
approved these changes
May 12, 2024
bingwang-ms
approved these changes
Aug 20, 2024
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
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.
Skip it by github issue #11403 on dualtor-64 topology
Description of PR
Skip dualtor/test_tunnel_memory_leak.py by github issue #11403 on dualtor-64 topology
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Script dualtor/test_tunnel_memory_leak.py not stable on dualtor-64 topology.
How did you do it?
Skip dualtor/test_tunnel_memory_leak.py by github issue #11403 on dualtor-64 topology
How did you verify/test it?
Run it in internal regression
Any platform specific information?
No
Supported testbed topology if it's a new test case?
Documentation