Skip to content

Skip vxlan bfd tsa testcase4/5/6 due to issue#15728#15978

Merged
liat-grozovik merged 2 commits intosonic-net:masterfrom
congh-nvidia:skip_test
Dec 24, 2024
Merged

Skip vxlan bfd tsa testcase4/5/6 due to issue#15728#15978
liat-grozovik merged 2 commits intosonic-net:masterfrom
congh-nvidia:skip_test

Conversation

@congh-nvidia
Copy link
Contributor

@congh-nvidia congh-nvidia commented Dec 10, 2024

Description of PR

Summary:
Skip vxlan bfd tsa testcases 4/5/6 due to issue(#15728)

Type of change

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

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405
  • 202411

Approach

What is the motivation for this PR?

Skip vxlan bfd tsa testcases 4/5/6 due to issue(#15728)

How did you do it?

Skip file on github issue

How did you verify/test it?

Rerun the test and see it is skipped

Any platform specific information?

All

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

Documentation

@liat-grozovik liat-grozovik changed the title [Nvidia] Skip vxlan bfd tsa testcase4/5/6 on Nvidia platforms [Mellanox] Skip vxlan bfd tsa testcase4/5/6 on Nvidia platforms Dec 11, 2024
Copy link
Contributor

@roy-sror roy-sror left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test should be skipped on all platforms as of test instability

This should be a common test issue that affects all platforms.
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@congh-nvidia congh-nvidia changed the title [Mellanox] Skip vxlan bfd tsa testcase4/5/6 on Nvidia platforms Skip vxlan bfd tsa testcase4/5/6 due to issue#15728 Dec 18, 2024
@congh-nvidia
Copy link
Contributor Author

The test should be skipped on all platforms as of test instability

Done.

@congh-nvidia
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@bingwang-ms
Copy link
Collaborator

@siqbal1986 Please help confirm skipping these tests won't lost coverage. Thanks!

@liat-grozovik liat-grozovik changed the title Skip vxlan bfd tsa testcase4/5/6 due to issue#15728 [Mellanox] Skip vxlan bfd tsa testcase4/5/6 due to issue#15728 Dec 24, 2024
@liat-grozovik liat-grozovik changed the title [Mellanox] Skip vxlan bfd tsa testcase4/5/6 due to issue#15728 Skip vxlan bfd tsa testcase4/5/6 due to issue#15728 Dec 24, 2024
@liat-grozovik liat-grozovik merged commit 0f5fb0f into sonic-net:master Dec 24, 2024
mssonicbld pushed a commit to mssonicbld/sonic-mgmt that referenced this pull request Mar 10, 2025
- What is the motivation for this PR?
Skip vxlan bfd tsa testcases 4/5/6 due to issue(sonic-net#15728)

- How did you do it?
Skip file on github issue

- How did you verify/test it?
Rerun the test and see it is skipped
@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202411: #17435

@mramezani95
Copy link
Contributor

Hi @congh-nvidia and @nhe-NV,
Is it necessary to skip this test on all platforms? If it is simply a test case issue, is it possible to fix the test case instead of skipping these tests?

@kperumalbfn
Copy link
Collaborator

@nhe-NV We shouldn't skip for all the platforms. For slower CPU SKUs, can we add some delay to improve the test success rate. Could you please check

@kperumalbfn
Copy link
Collaborator

@mramezani95

kperumalbfn added a commit that referenced this pull request Mar 13, 2025
nnelluri-cisco pushed a commit to nnelluri-cisco/sonic-mgmt that referenced this pull request Mar 15, 2025
- What is the motivation for this PR?
Skip vxlan bfd tsa testcases 4/5/6 due to issue(sonic-net#15728)

- How did you do it?
Skip file on github issue

- How did you verify/test it?
Rerun the test and see it is skipped
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.

8 participants