[Cherry Pick] 202012 Fix dual-tor dhcpv6 relay test cases failure #9960
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
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jcaiMR
force-pushed
the
dev/jcai_cherry_pick_202012_dhcpv6_dualtor
branch
from
1366777 to
f757133
Compare
kellyyeh
approved these changes
Sep 14, 2023
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.
Summary:
Cherry pick (#9842) to 202012
Type of change
Back port request
Approach
What is the motivation for this PR?
Cherry pick (#9842) to 202012
Code gap is big, solution refined based on 202012 base code.
How did you do it?
How did you verify/test it?
dhcp_relay/test_dhcpv6_relay.py::test_dhcp_relay_default
dhcp_relay/test_dhcpv6_relay.py::test_dhcpv6_relay_counter
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation