Skip to content

[action] [PR:18674] [dualtor] Fix loganalyzer not exist issue#18695

Merged
mssonicbld merged 1 commit intosonic-net:202411from
mssonicbld:cherry/202411/18674
May 29, 2025
Merged

[action] [PR:18674] [dualtor] Fix loganalyzer not exist issue#18695
mssonicbld merged 1 commit intosonic-net:202411from
mssonicbld:cherry/202411/18674

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

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505

Approach

What is the motivation for this PR?

If loganalyzer is not enabled, fixture loganalyzer will return None.

Signed-off-by: Longxiang Lyu [email protected]

How did you do it?

If loganalyzer is None, simply return.

How did you verify/test it?

Any platform specific information?

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

Documentation

@mssonicbld
Copy link
Copy Markdown
Collaborator Author

Original PR: #18674

@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 763c1b3 into sonic-net:202411 May 29, 2025
14 checks passed
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.

2 participants