Do not print route info in wait_for_ipv6_bgp_routes_recovery#19289
Do not print route info in wait_for_ipv6_bgp_routes_recovery#19289yxieca merged 1 commit intosonic-net:masterfrom
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi @w1nda , could you help review the PR, thanks! |
|
LGTM If we don't print, how can we debug routes? |
Change-Id: Ice438450be79f0d61936f8ffd1682752cb7f10a1
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @w1nda , I update function With this change, for test case This is the log example |
|
Hi @bingwang-ms @yxieca , could you help review this PR and add 202412 lable? |
|
Hi @bingwang-ms @yxieca , could you help review and add 202412 label |
|
@weiguo-nvidia please fill in the PR comment template. especially following fields: What is the motivation for this PR? |
I have updated the template, please help review again, thanks! |
|
@yxieca - your approval is required, following the recent fixes |
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass
|
Cherry-pick PR to 202505: #19667 |
How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass Signed-off-by: opcoder0 <[email protected]>
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass Signed-off-by: Guy Shemesh <[email protected]>
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass Signed-off-by: Aharon Malkin <[email protected]>
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass Signed-off-by: Guy Shemesh <[email protected]>
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass Signed-off-by: Guy Shemesh <[email protected]>
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass Signed-off-by: Yael Tzur <[email protected]>
…et#19289) How did you do it? Do not print route info in function wait_for_ipv6_bgp_routes_recovery Add log in function compare_routes to print the different routes How did you verify/test it? Run the case locally, pass
Description of PR
Summary: Do not print route info in function
wait_for_ipv6_bgp_routes_recoveryFixes #
The
wait_for_ipv6_bgp_routes_recoveryfunction prints the routing information in the log. However, in the 512 scale setup, due to the large routing scale, the log size exceeds 120M and is difficult to view. So do not print it.Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
wait_for_ipv6_bgp_routes_recoverycompare_routesto print the different routesHow did you verify/test it?
Run the case locally, pass
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation