Skip to content

[action] [PR:17985] [tests_mark_conditions.yaml]: Skip GNMI/ZMQ test for isolated topology#281

Merged
mssonicbld merged 1 commit intoAzure:202412from
mssonicbld:cherry/msft-202412/17985
May 15, 2025
Merged

[action] [PR:17985] [tests_mark_conditions.yaml]: Skip GNMI/ZMQ test for isolated topology#281
mssonicbld merged 1 commit intoAzure:202412from
mssonicbld:cherry/msft-202412/17985

Conversation

@mssonicbld
Copy link
Copy Markdown
Collaborator

Description of PR

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

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

Approach

What is the motivation for this PR?

GNMI ZMQ has an issue in isolated topology, but fixing it is not a priority because it isn't used in isolated topology. So, just skip this test.

How did you do it?

Add a condition in the skip file

How did you verify/test it?

Check locally

Any platform specific information?

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

Documentation

<!--
Please make sure you've read and understood our contributing guidelines;
https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md

Please provide following information to help code review process a bit easier:
-->
### Description of PR
<!--
- Please include a summary of the change and which issue is fixed.
- Please also include relevant motivation and context. Where should reviewer start? background context?
- List any dependencies that are required for this change.
-->

Summary:
Fixes # (issue)

### Type of change

<!--
- Fill x for your type of change.
- e.g.
- [x] Bug fix
-->

- [ ] Bug fix
- [ ] Testbed and Framework(new/improvement)
- [ ] New Test case
    - [ ] Skipped for non-supported platforms
- [ ] Test case improvement

### Back port request
- [ ] 202012
- [ ] 202205
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411

### Approach
#### What is the motivation for this PR?
GNMI ZMQ has an issue in isolated topology, but fixing it is not a priority because it isn't used in isolated topology. So, just skip this test.

#### How did you do it?
Add a condition in the skip file

#### How did you verify/test it?
Check locally

#### Any platform specific information?

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

### Documentation
<!--
(If it's a new feature, new test case)
Did you update documentation/Wiki relevant to your implementation?
Link to the wiki page?
-->
@mssonicbld
Copy link
Copy Markdown
Collaborator Author

Original PR: sonic-net/sonic-mgmt#17985

@mssonicbld
Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld mssonicbld merged commit d8b9193 into Azure:202412 May 15, 2025
4 of 7 checks passed
Javier-Tan added a commit that referenced this pull request May 16, 2025
```
81505c8 (az_upstream/202412) Merge branch '202411' of https://github.com/sonic-net/sonic-mgmt into 202412
30b7d73 (pub_upstream/202411) [202411 ] Updating the BGP, Reboot and LACP  convergence cases to latest Snappi Api Model instead of Snappi_convergence module [ PR 18044 ] (#18391)
e146100 [action] [PR:18292] Fix Skip tests if no portchannels are found in prepare_test_port fixture (#280)
d8b9193 [action] [PR:17985] [tests_mark_conditions.yaml]: Skip GNMI/ZMQ test for isolated topology (#281)
ef951e6 [action] [PR:17943] Add default routes to t1-isolated-d128 (#282)
2d3aec5 [action] [PR:18341] [route/test_route_perf] Support reading l3_alpm_template from config.bcm for TH5 platforms (#284)
6390c7d [202412][PR: 18350] disable default pfcwd for all lossy DUT (#271)
b621644 [Cherry-pick] modifying Ignore message for 'Failed to get port by bridge port ID' (#263)
bc9a2d2 modifying Ignore message for 'Failed to get port by bridge port ID'
```
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.

1 participant