[SERVER-60114] Audit recent coverity reports to see how many could be caught with v4 clang-tidy Created: 21/Sep/21  Updated: 28/Aug/23  Resolved: 28/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Development Platform
Participants:

 Description   

It would be helpful if our clang-tidy pass identified issues like those that coverity flagged in SERVER-59896 so that patch build runs would identify such erroneous code before it was merged.



 Comments   
Comment by Andrew Morrow (Inactive) [ 22/Sep/21 ]

I've updated the title of this issue, because I think what we actually ought to do is look at something like the last 6 months of coverity reports, and see how many of those reports have clang-tidy passes that could have identified the same issue. For any that do, we should attempt to enable the new clang-tidy pass.

Generated at Thu Feb 08 05:48:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.