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

[Mellanox] Update sensors.conf of SN5610N, SN5640 platforms #21972

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

noaOrMlnx
Copy link
Collaborator

Why I did it

To have the updated sensors.conf for SN5610N and SN5640 Mellanox platforms

How I did it

Took the last updated file from Hw mgmt package

How to verify it

Run platform test with latest file

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@noaOrMlnx noaOrMlnx force-pushed the mellanox-sensors-fix branch from 01455c8 to 57e876a Compare March 12, 2025 07:01
@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@liat-grozovik
Copy link
Collaborator

@noaOrMlnx can you check the failures?
are they generic and need to inform the maintainers?

also, do we need the test alignment? if so, need to tag the PR

@noaOrMlnx
Copy link
Collaborator Author

/azpw run Azure.sonic-buildimage

@mssonicbld
Copy link
Collaborator

/AzurePipelines run Azure.sonic-buildimage

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@noaOrMlnx
Copy link
Collaborator Author

@noaOrMlnx can you check the failures? are they generic and need to inform the maintainers?

also, do we need the test alignment? if so, need to tag the PR

@liat-grozovik
Failure seem to happen because of a timeout, I rerun the tests and in case it will fail again I will ask Build admin to check that.
Regarding test alignment, there is one, but currently it's internal. It is planned to be upstreamed by end of month.

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