-
Notifications
You must be signed in to change notification settings - Fork 737
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
BGP Convergence Test for Benchmark Performance #3715
Conversation
Get latest changes
This pull request introduces 3 alerts when merging 13ff5fe18c2fabb7b8f624c54299d10b43bafd8c into ca982e6 - view on LGTM.com new alerts:
|
13ff5fe
to
8629730
Compare
This pull request introduces 6 alerts when merging 8629730 into dff9522 - view on LGTM.com new alerts:
|
Can you fix the testing failures related with this change? It would be great if you can fix the LGTM alerts as well.
|
@wangxin Raised a PR sonic-net/sonic-buildimage#8030 for snappi_convergence module |
This pull request introduces 3 alerts when merging ec60200 into 1b53581 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 20e20be into 1b53581 - view on LGTM.com new alerts:
|
Azure Pipelines successfully started running 1 pipeline(s). |
@wangxin can you please merge sonic-net/sonic-buildimage#9682. |
PR sonic-net/sonic-buildimage#9682 has been merged, lets wait for a new sonic-mgmt docker image. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@wangxin I have updated the BGP scripts for the latest snappi version and raised a PR sonic-net/sonic-buildimage#9932 for snappi version 0.7.12 , can you please merge the PR 9932 and create a new sonic-mgmt docker image, after which the pipeline may pass |
This pull request introduces 1 alert when merging 89ece91 into 7a8be07 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 326464e into 3acec36 - view on LGTM.com new alerts:
|
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@wangxin The checks were successful before, now i see some checks are not successful, the results shows the test setup failure. Can this be resolved and merged |
@selldinesh I am not able to merge this PR until all tests passed. Lets give it another try. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
This pull request introduces 2 alerts when merging a4ec6a5 into f28a6c3 - view on LGTM.com new alerts:
|
@@ -941,5 +941,5 @@ def cleanup_config(duthost): | |||
duthost.command("sudo cp {} {}".format("/etc/sonic/config_db_backup.json","/etc/sonic/config_db.json")) | |||
duthost.shell("sudo config reload -y \n") | |||
logger.info("Wait until all critical services are fully started") | |||
pytest_assert(wait_until(360, 10, 1, duthost.critical_services_fully_started), "Not all critical services are fully started") | |||
pytest_assert(wait_until(360, 10, duthost.critical_services_fully_started), "Not all critical services are fully started") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am afraid that this change won't work. The LGTM also raised alert "Wrong number of arguments in a call".
The wait_until
function has been improved to support initial delay. Unfortunately the change is not backward compatible. The author has made a swept change. But all the open PRs still suffer from this issue.
This is the new signature of the wait_until
function: https://github.com/Azure/sonic-mgmt/blob/master/tests/common/utilities.py#L82
For the wait_until
to work in your local setup, can you do a rebase to the latest master branch and make a force push
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wangxin i have reverted the changes back for the wait_until function
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
This pull request introduces 1 alert when merging 2a47fcf into 5fecae8 - view on LGTM.com new alerts:
|
Description of PR
Summary:BGP Convergence Test for Benchmark Performance
BGP Failover convergence for remote link failure
BGP RIB-IN Convergence
BGP RIB-IN Capacity
BGP Failover convergence for Local Link Failure
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation
https://github.com/Azure/sonic-mgmt/blob/master/docs/testplan/BGP%20Convergence%20Testplan%20for%20single%20DUT.md#test-case--1--convergence-performance-when-remote-link-fails-route-withdraw