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

janga800bic : added led_manager.json #218

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

GoravGargCelestica
Copy link
Contributor

@GoravGargCelestica GoravGargCelestica commented Sep 5, 2024

Description

Added led_manager.json file to verify the data_corral_service and the data_corral_service_hw_test.

Motivation

Aim is to verify the data_corral_service and the data_corral_service_hw_test.

Testing

Data Corral Service Logs : j3_data_corral_service_logs.txt

Data Corral Service HW Test Logs : j3_data_corral_service_hw_test_logs.txt

@facebook-github-bot
Copy link
Contributor

Hi @GoravGargCelestica!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@facebook-github-bot
Copy link
Contributor

@mikechoifb has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@kimdo8736
Copy link

Hi, please remove the following

"chassisEepromName" : "CHASSIS" ,
"fruEepromList" : {
"CHASSIS" : {
"path" : "/run/devmap/eeproms/COME_EEPROM"
}
},

This is weutil.json contents. Please apply the same fixes for tahan and montblanc. Thanks.

@GoravGargCelestica
Copy link
Contributor Author

Hi, please remove the following

"chassisEepromName" : "CHASSIS" , "fruEepromList" : { "CHASSIS" : { "path" : "/run/devmap/eeproms/COME_EEPROM" } },

This is weutil.json contents. Please apply the same fixes for tahan and montblanc. Thanks.

Hi @kimdo8736

Thankyou for your feedback.
We have added this EEPROM content intentionally to avoid failures while running the data_corral_service_hw_test suite. Without this, test suite has the following error:

C++ exception with description "std::runtime_error: Invalid EEPROM name CHASSIS. Valid EEPROM names are: " thrown in the test body.

Complete Log: fail_data_corral_service_hw_test_log.txt

After adding it the test suite is passed successfully : pass_data_corral_service_hw_test_log.txt

Please let me know your comment.

@kimdo8736
Copy link

Thanks for the response, with this commit (dff361d)

You can now run without the EEPROM contents. Please let me know how that goes on your end. Thanks.

@facebook-github-bot
Copy link
Contributor

@GoravGargCelestica has updated the pull request. You must reimport the pull request before landing.

@GoravGargCelestica
Copy link
Contributor Author

GoravGargCelestica commented Sep 18, 2024

Thanks for the response, with this commit (dff361d)

You can now run without the EEPROM contents. Please let me know how that goes on your end. Thanks.

Hi @kimdo8736 ,

Thanks for your feedback.
Yes, with the recent commit (dff361d) there is no need to have the EEPROM content in the led_manager.json , I have updated the changes. Also, attached the latest testing result in the PR description, please help to review again.

I have updated Tahan and Montblanc PRs too.

Thanks,
Gorav.

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.

3 participants