Skip to content
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

[lag_rate] Restore lag setting on VMs in case of failure in test #839

Merged
merged 1 commit into from
Mar 28, 2019
Merged

[lag_rate] Restore lag setting on VMs in case of failure in test #839

merged 1 commit into from
Mar 28, 2019

Conversation

wangxin
Copy link
Collaborator

@wangxin wangxin commented Mar 22, 2019

Description of PR

Summary:
Fixes # (issue)

The existing script does not restore lag rate setting on VMs in case
of failure. This improvement is to restore lag setting on VMs if the
testing failed.

Type of change

  • Bug fix
  • [] Testbed and Framework(new/improvement)
  • [] Test case(new/improvement)

Approach

How did you do it?

Wrap the lag rate testing code in block. Add always section to restore VMs settings in case the settings are not restored in testing.

How did you verify/test it?

Tested on Mellanox platform.

Any platform specific information?

No.

Supported testbed topology if it's a new test case?

Documentation

The existing script does not restore lag rate setting on VMs in case
of failure. This improvement is to restore lag setting on VMs if the
testing failed.

Signed-off-by: Xin Wang <xinw@mellanox.com>
@liat-grozovik liat-grozovik merged commit 206afe4 into sonic-net:master Mar 28, 2019
yxieca pushed a commit that referenced this pull request Mar 28, 2019
The existing script does not restore lag rate setting on VMs in case
of failure. This improvement is to restore lag setting on VMs if the
testing failed.

Signed-off-by: Xin Wang <xinw@mellanox.com>
@wangxin wangxin deleted the lag-rate-pr branch May 24, 2019 03:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants