Skip to content

RDKB-62102, RDKB-61923: High impact Coverity bugs - ccsp-common-library-1#48

Merged
snayak002c merged 2 commits intodevelopfrom
feature/RDKB-61923
Dec 18, 2025
Merged

RDKB-62102, RDKB-61923: High impact Coverity bugs - ccsp-common-library-1#48
snayak002c merged 2 commits intodevelopfrom
feature/RDKB-61923

Conversation

@ksures101
Copy link
Copy Markdown
Contributor

@ksures101 ksures101 commented Dec 3, 2025

Reason for change: To address coverity issues
Test Procedure: There should not be any coverity issues mentioned in the ticket
Risks: None
Priority: P1

Signed-off-by: kavyachowdahalli_suresh@comcast.com

@ksures101 ksures101 requested review from a team as code owners December 3, 2025 17:02
@ksures101 ksures101 force-pushed the feature/RDKB-61923 branch 4 times, most recently from 8059f5a to 1e991da Compare December 5, 2025 16:58
@ksures101 ksures101 changed the title RDKB-61923: High impact Coverity bugs - ccsp-common-library-1 RDKB-62302, RDKB-62102: High impact Coverity bugs - ccsp-common-library-1 Dec 9, 2025
@ksures101 ksures101 changed the title RDKB-62302, RDKB-62102: High impact Coverity bugs - ccsp-common-library-1 RDKB-62102, RDKB-61923: High impact Coverity bugs - ccsp-common-library-1 Dec 9, 2025
@ksures101
Copy link
Copy Markdown
Contributor Author

  1. Is this a Bug or a User Story (US)? It's, a User Story PR
  2. If it is a User Story:
    • Have all dependent PRs from other components been listed (if any)? Yes
    • Does the commit message include both the User Story ticket and the Subtask ticket? Yes
    • Will be all changes related to the User Story squashed and merged in a single commit? Yes
    • Has the PR been raised only after completing all changes for the User Story (no partial changes)? Yes
    • Has code development for the User Story been completed? Yes
      • If yes, has the Gerrit topic or list of all dependent PRs across components (including meta-layer changes) been shared? Yes
  3. Is there a validation log available in the Jira ticket for verifying builds with the updated generic-srcrev.inc across all platforms? Yes

Reason for change: To address coverity issues
Test Procedure:
1. There should not be any coverity issues mentioned in the ticket
Risks: None
Priority: P1

Signed-off-by: kavyachowdahalli_suresh@comcast.com
@snayak002c snayak002c merged commit 8d2cc6b into develop Dec 18, 2025
7 of 9 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Dec 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants