-
Notifications
You must be signed in to change notification settings - Fork 582
Gcov for swss daemon #1737
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
Gcov for swss daemon #1737
Conversation
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
…ragilenetworks/sonic-swss into gcov_for_swss_daemon
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Commenter does not have sufficient privileges for PR 1737 in repo Azure/sonic-swss |
@prsunny help forward,have rebuild done! |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/Azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/Azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
hi @prsunny @theasianpianist help forward this, thanks! |
/Azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@xumia , could you please sign-off ? |
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.
after this will be merged, may we check how much coverage this will generate for sonic-sairedis repo ? currently sairedis repo only runs local unittests which cover about 60% of the code, maybe running docker tests will bump that number up
@pettershao-ragilenetworks hey, can we try use this approach on sonic-sairedis repo ? to find out what coverage could be achieved, since current unittest cover on sairedis repo in 60%, i will write mail |
OK! |
Signed-off-by: bingwang <[email protected]>
include changes: 0031470 | improve enum values integration check (sonic-net#1727) (sonic-net#1737) Signed-off-by: richardyu-ms <[email protected]>
What I did
Introduce gcov-related automation script to test coverage rate for swss module
relate HLD: sonic-net/SONiC#642
Why I did it
Attempt to integrate coverage report for each module in SONiC to Azure pipeline
How I verified it
Using Azure pipeline to check whether a coverage report can be checked after a pull request
Details if related