Skipped IPv6 Everflow tests on virtual switch to speed up PR test execution#18539
Merged
wangxin merged 1 commit intosonic-net:masterfrom May 22, 2025
Merged
Conversation
Signed-off-by: Mahdi Ramezani <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
xwjiang-ms
approved these changes
May 22, 2025
yutongzhang-microsoft
approved these changes
May 22, 2025
wangxin
approved these changes
May 22, 2025
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
May 22, 2025
What is the motivation for this PR? Everflow tests take a lot of time to execute. After adding IPv6 test cases (sonic-net#16836), the execution time has roughly doubled. Now it takes more than 2 hours to run all tests in everflow/test_everflow_testbed.py. Since these tests are part of PR tests, if they take too long to run, the PR test will be cancelled. This PR skips the IPv6 Everflow tests on KVM testbeds (which are used for PR tests) to address this issue. Note: The IPv6 Everflow tests will still run during nightly tests. How did you do it? Added a new pytest fixture that will skip the tests when erspan_ip_ver == 6 and the DUT is a virtual switch. How did you verify/test it? Ran the tests to ensure that the tests will be skipped when erspan_ip_ver == 6. Any platform specific information? Only applies to KVM testbeds ("vs" ASIC). Signed-off-by: Mahdi Ramezani <[email protected]>
Collaborator
|
Cherry-pick PR to 202505: #18546 |
11 tasks
yejianquan
pushed a commit
that referenced
this pull request
May 22, 2025
What is the motivation for this PR? Everflow tests take a lot of time to execute. After adding IPv6 test cases (#16836), the execution time has roughly doubled. Now it takes more than 2 hours to run all tests in everflow/test_everflow_testbed.py. Since these tests are part of PR tests, if they take too long to run, the PR test will be cancelled. This PR skips the IPv6 Everflow tests on KVM testbeds (which are used for PR tests) to address this issue. Note: The IPv6 Everflow tests will still run during nightly tests. How did you do it? Added a new pytest fixture that will skip the tests when erspan_ip_ver == 6 and the DUT is a virtual switch. How did you verify/test it? Ran the tests to ensure that the tests will be skipped when erspan_ip_ver == 6. Any platform specific information? Only applies to KVM testbeds ("vs" ASIC). Signed-off-by: Mahdi Ramezani <[email protected]> Co-authored-by: mramezani95 <[email protected]>
mssonicbld
added
Included in 202505 branch
and removed
Created PR to 202505 branch
labels
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
May 22, 2025
What is the motivation for this PR? Everflow tests take a lot of time to execute. After adding IPv6 test cases (sonic-net#16836), the execution time has roughly doubled. Now it takes more than 2 hours to run all tests in everflow/test_everflow_testbed.py. Since these tests are part of PR tests, if they take too long to run, the PR test will be cancelled. This PR skips the IPv6 Everflow tests on KVM testbeds (which are used for PR tests) to address this issue. Note: The IPv6 Everflow tests will still run during nightly tests. How did you do it? Added a new pytest fixture that will skip the tests when erspan_ip_ver == 6 and the DUT is a virtual switch. How did you verify/test it? Ran the tests to ensure that the tests will be skipped when erspan_ip_ver == 6. Any platform specific information? Only applies to KVM testbeds ("vs" ASIC). Signed-off-by: Mahdi Ramezani <[email protected]>
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
What is the motivation for this PR? Everflow tests take a lot of time to execute. After adding IPv6 test cases (sonic-net#16836), the execution time has roughly doubled. Now it takes more than 2 hours to run all tests in everflow/test_everflow_testbed.py. Since these tests are part of PR tests, if they take too long to run, the PR test will be cancelled. This PR skips the IPv6 Everflow tests on KVM testbeds (which are used for PR tests) to address this issue. Note: The IPv6 Everflow tests will still run during nightly tests. How did you do it? Added a new pytest fixture that will skip the tests when erspan_ip_ver == 6 and the DUT is a virtual switch. How did you verify/test it? Ran the tests to ensure that the tests will be skipped when erspan_ip_ver == 6. Any platform specific information? Only applies to KVM testbeds ("vs" ASIC). Signed-off-by: Mahdi Ramezani <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
What is the motivation for this PR? Everflow tests take a lot of time to execute. After adding IPv6 test cases (sonic-net#16836), the execution time has roughly doubled. Now it takes more than 2 hours to run all tests in everflow/test_everflow_testbed.py. Since these tests are part of PR tests, if they take too long to run, the PR test will be cancelled. This PR skips the IPv6 Everflow tests on KVM testbeds (which are used for PR tests) to address this issue. Note: The IPv6 Everflow tests will still run during nightly tests. How did you do it? Added a new pytest fixture that will skip the tests when erspan_ip_ver == 6 and the DUT is a virtual switch. How did you verify/test it? Ran the tests to ensure that the tests will be skipped when erspan_ip_ver == 6. Any platform specific information? Only applies to KVM testbeds ("vs" ASIC). Signed-off-by: Mahdi Ramezani <[email protected]> Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
What is the motivation for this PR? Everflow tests take a lot of time to execute. After adding IPv6 test cases (sonic-net#16836), the execution time has roughly doubled. Now it takes more than 2 hours to run all tests in everflow/test_everflow_testbed.py. Since these tests are part of PR tests, if they take too long to run, the PR test will be cancelled. This PR skips the IPv6 Everflow tests on KVM testbeds (which are used for PR tests) to address this issue. Note: The IPv6 Everflow tests will still run during nightly tests. How did you do it? Added a new pytest fixture that will skip the tests when erspan_ip_ver == 6 and the DUT is a virtual switch. How did you verify/test it? Ran the tests to ensure that the tests will be skipped when erspan_ip_ver == 6. Any platform specific information? Only applies to KVM testbeds ("vs" ASIC). Signed-off-by: Mahdi Ramezani <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
What is the motivation for this PR? Everflow tests take a lot of time to execute. After adding IPv6 test cases (sonic-net#16836), the execution time has roughly doubled. Now it takes more than 2 hours to run all tests in everflow/test_everflow_testbed.py. Since these tests are part of PR tests, if they take too long to run, the PR test will be cancelled. This PR skips the IPv6 Everflow tests on KVM testbeds (which are used for PR tests) to address this issue. Note: The IPv6 Everflow tests will still run during nightly tests. How did you do it? Added a new pytest fixture that will skip the tests when erspan_ip_ver == 6 and the DUT is a virtual switch. How did you verify/test it? Ran the tests to ensure that the tests will be skipped when erspan_ip_ver == 6. Any platform specific information? Only applies to KVM testbeds ("vs" ASIC). Signed-off-by: Mahdi Ramezani <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
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
6 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:
This PR skips the IPv6 Everflow tests on KVM testbeds to improve PR test execution time.
Type of change
Back port request
Approach
What is the motivation for this PR?
Everflow tests take a lot of time to execute. After adding IPv6 test cases (#16836), the execution time has roughly doubled. Now it takes more than 2 hours to run all tests in
everflow/test_everflow_testbed.py. Since these tests are part of PR tests, if they take too long to run, the PR test will be cancelled. This PR skips the IPv6 Everflow tests on KVM testbeds (which are used for PR tests) to address this issue.Note: The IPv6 Everflow tests will still run during nightly tests.
How did you do it?
Added a new pytest fixture that will skip the tests when
erspan_ip_ver == 6and the DUT is a virtual switch.How did you verify/test it?
Ran the tests to ensure that the tests will be skipped when
erspan_ip_ver == 6.Any platform specific information?
Only applies to KVM testbeds ("vs" ASIC).
Supported testbed topology if it's a new test case?
N/A
Documentation
N/A