[action] [PR:20932] Adjusting test_stress_arp is it can handle cases of ipv6-only topologies .#22112
Open
mssonicbld wants to merge 1 commit intosonic-net:202511from
Open
[action] [PR:20932] Adjusting test_stress_arp is it can handle cases of ipv6-only topologies .#22112mssonicbld wants to merge 1 commit intosonic-net:202511from
mssonicbld wants to merge 1 commit intosonic-net:202511from
Conversation
…ies . (sonic-net#20932) In IPv6-only topologies, use 'ip -6 neigh flush all' insted of 'ip -stats neigh flush all' to make it more focus on IPv6 only, and reduce the chance of unsuccessful execution of a command. Add skip for test_ipv4_arp in case of ipv6 only topology.
11 tasks
Collaborator
Author
|
/azp run |
Collaborator
Author
|
Original PR: #20932 |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-mgmt |
1 similar comment
|
/azpw run Azure.sonic-mgmt |
Collaborator
Author
|
/AzurePipelines run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@gshemesh2, Please check pre-commit checks are failing as part of the PR Pre-commit check failure logs: @vmittal-msft, FYI |
This was referenced Mar 8, 2026
Pterosaur
added a commit
to Pterosaur/sonic-mgmt
that referenced
this pull request
Mar 8, 2026
Remove duplicate 'bgp/test_bgp_vnet.py' entry (lines 485-490) which is identical to the first occurrence (lines 479-484). The duplicate key causes check-yaml pre-commit hook failures on all PRs that modify this file. This unblocks PRs sonic-net#22793, sonic-net#22779, sonic-net#22321, sonic-net#22112, sonic-net#22041, sonic-net#22006. Signed-off-by: Ze Gan <ganze718@gmail.com>
vmittal-msft
pushed a commit
that referenced
this pull request
Mar 9, 2026
Remove duplicate 'bgp/test_bgp_vnet.py' entry (lines 485-490) which is identical to the first occurrence (lines 479-484). The duplicate key causes check-yaml pre-commit hook failures on all PRs that modify this file. This unblocks PRs #22793, #22779, #22321, #22112, #22041, #22006. Signed-off-by: Ze Gan <ganze718@gmail.com>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Adjusting test_stress_arp is it can handle cases of ipv6-only topologies .
How did you do it?
In IPv6-only topologies, use 'ip -6 neigh flush all' insted of 'ip -stats neigh flush all' to make it more focus on IPv6 only, and reduce the chance of unsuccessful execution of a command.
Add skip for test_ipv4_arp in case of ipv6 only topology.
How did you verify/test it?
Ran it on Nvidia platforms in IPv6 and IPv4 topologies.
Any platform specific information?
No
Supported testbed topology if it's a new test case?
IPv6 and IPv4 topologies.
Documentation