Swss gcov support #1738
Draft
Swss gcov support #1738
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
|
can you check the here. your azp changes has syntax error. https://dev.azure.com/mssonic/build/_build?definitionId=15 |
|
This pull request introduces 4 alerts when merging 61c2456 into c37cc1c - view on LGTM.com new alerts:
|
Signed-off-by: pettershao-ragilenetworks <[email protected]>
Signed-off-by: pettershao-ragilenetworks <[email protected]>
|
This pull request introduces 4 alerts when merging 117f241 into c37cc1c - view on LGTM.com new alerts:
|
|
This pull request introduces 4 alerts when merging 5670006 into c37cc1c - view on LGTM.com new alerts:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I did
Introduce gcov-related automation script to test coverage rate for swss module
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