-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[sonic-pit] Add PIT(Platform Integration Test) feature, initial commi… #12441
[sonic-pit] Add PIT(Platform Integration Test) feature, initial commi… #12441
Conversation
…t, with only framework and 2 test cases with 1 supportting platform. Signed-off-by: Li Hua <guizhao.lh@alibaba-inc.com>
This pull request introduces 16 alerts when merging c1ae72b into bc8ee7a - view on LGTM.com new alerts:
|
This pull request introduces 16 alerts when merging e8ae2a6 into fff6808 - view on LGTM.com new alerts:
|
This pull request introduces 16 alerts when merging ed20ee8 into fff6808 - view on LGTM.com new alerts:
|
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
This pull request introduces 16 alerts when merging 8a4b0a4 into fff6808 - view on LGTM.com new alerts:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CodeQL found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.
This pull request introduces 16 alerts when merging a60eaa4 into 81ee948 - view on LGTM.com new alerts:
|
This pull request introduces 6 alerts when merging 493d565 into 81ee948 - view on LGTM.com new alerts:
|
This pull request introduces 6 alerts when merging 5e2f98b into dad3f61 - view on LGTM.com new alerts:
|
close this one, replace with #12514. |
…t, with only framework and 2 test cases with 1 supportting platform.
Signed-off-by: Li Hua guizhao.lh@alibaba-inc.com
Why I did it
sonic-pit is originated from S3IP(Simplify Switch System Integration Program) PIT(Platform Integration Test). It's designed to verify switch devices in the process of development, manufacturing and delivering stages. It focus on 2 roles: ODM and user. ODM may use PIT in developing and manufaturing stages, user may use PIT in delivery stage for acceptance test. It aims to provide an verify system for siwtch devices' hardware, drivers and firmware. More information, see HLD: https://github.com/clarklee-guizhao/SONiC/blob/pit/doc/pit/Platform_Integration_Test_high_level_design.md
How I did it
Porting sonic-pit from S3IP-PIT, make the original code clean enough, add PIT source as sonic-pit, add PIT running environment as docker-pit.
The whole PIT system is divided into several PR, this is the first PR with PIT framework and 2 test cases with 1 supporting platform only.
How to verify it
Build docker docker-pit, deploy it onto devices which support sonic-pit, run pit.
Which release branch to backport (provide reason below if selected)
Description for the changelog
Add PIT, whihc include sonic-pit(the PIT system) and docker-pit(the running environment for sonic-pit).
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)